Common: Separate NuGet packages so that a project can include only what is needed
Posted on:02 Mar 2018 11:40
Thank you for your comments.
The separate Nuget packages as well as the namespaces follow the way the controls are organized in assemblies. Wе have combined similar components (for example, input controls, data controls, etc) in a separate assemblies for a few reasons, such as to share code between them easily, to avoid referencing too many assemblies, etc.
Additionally, some components depend on other, for example RadNumericInput contains RadEntry, so in this case, if they were in separate assemblies, you would need to reference both and this would lead to confusion.
I hope I managed to clear this up. Let me know if you have any questions or concerns.
Posted on:06 Feb 2017 15:14
Would be nice if namespaces were broken out into a more logical naming convention too. Example: Telerik.XamarinForms.Input contains "Calendar" -> Telerik.XamarinForms.Calendar. This way I'm only loading which controls I need for a project.
Posted on:06 Feb 2017 15:07
It would be nice to only load the controls that are necessary for a project. The Nuget packages should be a single reference (i.e Telerik.Xamarin.Chart) that loads the appropriate dependent namespaces according to project type (i.e Android or iOS, PCL).