[Feature Request]: An 'Ultimate' NuGet package

[PWagner1]

A new 'Ultimate' NuGet package, which includes all 5 modules in one.

[Smurf-IV]

Please state (And add a vote buttons?) what modules this may include.

[PWagner1]

Added a poll to Discord general channel

Poll: As part of v80 of the Standard Toolkit, would you like to have a 'Ultimate' NuGet package, which will consist of Toolkit, Ribbon, Navigator, Workspace and Docking all in one. React with :thumbsup: if you'd like to see this, otherwise :thumbsdown:. Please vote now.

[Smurf-IV]

Added a poll to Discord general channel

Can you add the link so that it can be found in a couple of days time - Thanks

[PWagner1]

Poll on Discord: Link

[ghost]

Even Extended-Toolkit-master should be combined into a single package

[ghost]

Added a poll to Discord general channel

Poll: As part of v80 of the Standard Toolkit, would you like to have a 'Ultimate' NuGet package, which will consist of Toolkit, Ribbon, Navigator, Workspace and Docking all in one. React with 👍 if you'd like to see this, otherwise 👎. Please vote now.

Hey every time I inherit I have to aggregate and normalize to Fluent form

[PWagner1]

Even Extended-Toolkit-master should be combined into a single package

@MarketingInternetOnlines It already is, please see https://www.nuget.org/packages/Krypton.Toolkit.Suite.Extended.Ultimate/ or https://www.nuget.org/packages/Krypton.Toolkit.Suite.Extended.Ultimate.Lite/

[PWagner1]

Hey every time I inherit I have to aggregate and normalize to Fluent form

@MarketingInternetOnlines Not sure that I follow, could you elaborate a bit more?

[ghost]

Even Extended-Toolkit-master should be combined into a single package

@MarketingInternetOnlines It already is, please see https://www.nuget.org/packages/Krypton.Toolkit.Suite.Extended.Ultimate/ or https://www.nuget.org/packages/Krypton.Toolkit.Suite.Extended.Ultimate.Lite/

This includes the most sub-projects, why don't you include it in a single project, Krypton.ExtendedToolkit, so that users are not confused and make the most of the library.

The reason why it's not a single project is that it's easier to manage. Also, having one project means a lot of duplication.

[ghost]

Each subproject is a directory, a good application contains a few .dll, taking advantage of each other's functions and classes.

[PWagner1]

Each subproject is a directory, a good application contains a few .dll, taking advantage of each other's functions and classes.

@MarketingInternetOnlines

We did try that pre .NET Core conversion, however the problem was managing one project as it was so huge. Also, not everyone needs/wants to use the entire toolkit. If there is a way to 'link' files to include in one project, so that one version of the file is edited, then maybe we can consider making one DLL.

[ghost]

Each subproject is a directory, a good application contains a few .dll, taking advantage of each other's functions and classes.

@MarketingInternetOnlines

We did try that pre .NET Core conversion, however the problem was managing one project as it was so huge. Also, not everyone needs/wants to use the entire toolkit. If there is a way to 'link' files to include in one project, so that one version of the file is edited, then maybe we can consider making one DLL.

Thank you very much, because the Extended-Toolkit library is inherited from the Standard-Toolkit library, expanded, so to use all that is in the Extended-Toolkit library in the most optimal way. I think it would be best to combine them, helping users in the project also control the library

[ghost]

Let's give users the best experience like apply did

[PWagner1]

@Smurf-IV Thoughts on this?

[Smurf-IV]

A few things:

1. the "Extended-Toolkit library" is not as well supported as the "base" toolkit
2. the "Extended-Toolkit library" pulls in a lot of third party nugets which some apps just don;t need in their footprint, or even might not agree to their licensing
3. there is nothing stopping the nuget for the "Extended-Toolkit library" parts from referencing the correct version of the "base" toolkit that it was intended to use
4. Create a monster "Extended-Toolkit library" nuget to allow the large download if it must be so.
5. Dedicate a lot more time to sorting the "Extended-Toolkit library" features and stability

Option 3 is the route to go, and this should be moved into the "Extended-Toolkit library" repo.

[PWagner1]

Setting this to `backlog'. Might be something to look at next year.