Difference between ookii-dialogs and ookii-dialogs-wpf? #15
-
Hi, As a first time user of ookii-dialogs, I'm wondering what's up with the different packages with different authors and sites. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Hi @ultimate-tester, what are the different packages with different authors and sites that you are referring to? The Ookii Dialogs project (both for WPF and WinForms) was originally created by Sven Groot in 2009, and it's being maintained by me since 2018 on these repos below:
The NuGet packages are, respectively: |
Beta Was this translation helpful? Give feedback.
-
Hi augustoproiete, Thanks for the quick response. So there's this package called "Ookii.Dialogs" and as I now understand the packages "Ookii.Dialogs.Wpf" and "Ooki.Dialogs.WinForms" are its succesors? So the "Ookii.Dialogs" is deprecated? It was just a little confusing when selecting packages, seeing a more popular (but older) package. I was just curious if the ".Wpf" version was a rip-off or an official version, but now I understand I should use the ".Wpf" version and not look at "Ookii.Dialogs" anymore. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Got it Indeed, the NuGet package I went to NuGet to search for packages with the same name and here is a summary:
(*) Not yet published in nuget.org. Will be published in the next few days. ps: I reached out to superkinhluan earlier today and he was nice enough to transfer the ownership of his |
Beta Was this translation helpful? Give feedback.
-
Thanks for the quick replies and action! Closed! |
Beta Was this translation helpful? Give feedback.
Got it☺️ . Thanks for bringing this to my attention.
Indeed, the NuGet package
Ookii.Dialogs
is deprecated. It was published by superkinhluan back in 2011 from the original code from Sven at that time and it accumulated a number of downloads over the years whilstOokii.Dialogs.Wpf
was only published years later in 2018 which is why it has a smaller number of downloads.I went to NuGet to search for packages with the same name and here is a summary: