You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we are using the SDK-style with multi-targeting and and have a good build pipeline setup, it would be easy to generate separate NuGet packages for each of the dialogs, so that developers can have the option to cherry-pick only the dialogs they want to use in their application.
Ookii.Dialogs.Wpf.nupkg, depends on:
Ookii.Dialogs.Wpf.TaskDialog.nupkg, depends on:
Ookii.Dialogs.Wpf.Core.nupkg, depends on:
Ookii.Dialogs.Core.nupkg(no dependencies)
Ookii.Dialogs.Wpf.ProgressDialog.nupkg, depends on:
Ookii.Dialogs.Wpf.Core.nupkg, depends on:
Ookii.Dialogs.Core.nupkg(no dependencies)
Ookii.Dialogs.Wpf.CredentialDialog.nupkg, depends on:
Ookii.Dialogs.Wpf.Core.nupkg, depends on:
Ookii.Dialogs.Core.nupkg(no dependencies)
Ookii.Dialogs.Wpf.FolderBrowserDialog.nupkg, depends on:
Ookii.Dialogs.Wpf.Core.nupkg, depends on:
Ookii.Dialogs.Core.nupkg(no dependencies)
Ookii.Dialogs.Wpf.OpenFileDialog.nupkg, depends on:
Ookii.Dialogs.Wpf.Core.nupkg, depends on:
Ookii.Dialogs.Core.nupkg(no dependencies)
Ookii.Dialogs.Wpf.SaveFileDialog.nupkg, depends on:
Ookii.Dialogs.Wpf.Core.nupkg, depends on:
Ookii.Dialogs.Core.nupkg(no dependencies)
I'm assuming we'll have to create a Ookii.Dialogs.Wpf.Core package to share common WPF code between the different WPF dialog packages, as well as a Ookii.Dialogs.Core package to share common code across both the WPF and WinForms packages (#27).
Turning Ookii.Dialogs.Wpf into a meta package that depends on all other micro packages will provide the same experience that users have today where they'll get all the dialogs with one package.
The text was updated successfully, but these errors were encountered:
Now that we are using the SDK-style with multi-targeting and and have a good build pipeline setup, it would be easy to generate separate NuGet packages for each of the dialogs, so that developers can have the option to cherry-pick only the dialogs they want to use in their application.
Ookii.Dialogs.Wpf.nupkg
, depends on:Ookii.Dialogs.Wpf.TaskDialog.nupkg
, depends on:Ookii.Dialogs.Wpf.Core.nupkg
, depends on:Ookii.Dialogs.Core.nupkg
(no dependencies)Ookii.Dialogs.Wpf.ProgressDialog.nupkg
, depends on:Ookii.Dialogs.Wpf.Core.nupkg
, depends on:Ookii.Dialogs.Core.nupkg
(no dependencies)Ookii.Dialogs.Wpf.CredentialDialog.nupkg
, depends on:Ookii.Dialogs.Wpf.Core.nupkg
, depends on:Ookii.Dialogs.Core.nupkg
(no dependencies)Ookii.Dialogs.Wpf.FolderBrowserDialog.nupkg
, depends on:Ookii.Dialogs.Wpf.Core.nupkg
, depends on:Ookii.Dialogs.Core.nupkg
(no dependencies)Ookii.Dialogs.Wpf.OpenFileDialog.nupkg
, depends on:Ookii.Dialogs.Wpf.Core.nupkg
, depends on:Ookii.Dialogs.Core.nupkg
(no dependencies)Ookii.Dialogs.Wpf.SaveFileDialog.nupkg
, depends on:Ookii.Dialogs.Wpf.Core.nupkg
, depends on:Ookii.Dialogs.Core.nupkg
(no dependencies)I'm assuming we'll have to create a
Ookii.Dialogs.Wpf.Core
package to share common WPF code between the different WPF dialog packages, as well as aOokii.Dialogs.Core
package to share common code across both the WPF and WinForms packages (#27).Turning
Ookii.Dialogs.Wpf
into a meta package that depends on all other micro packages will provide the same experience that users have today where they'll get all the dialogs with one package.The text was updated successfully, but these errors were encountered: