When I used Telerik WPF VS Extension to convert my project to Telerik WPF project there was a check box to 'Add referenced assemblies' to project.
When I checked that and chose the few assemblies I needed in my project, I discoverd that ALL the Telerik WPF assemblies have been copied to ...\lib\RCWPF\2013.2.611.40, not just the referenced assemblies as the check box stated. Also ALL the language assemblies were copied as well eventhough I do not intend to use localization.
When I build my solution now only the assemblies I referenced are copied to bin/Debug folders so why did the WPF VS Extenstion copy ALL the WPF assemblies to my solution and can I just waste my time tracking down assemblies I do not need and delete them?
Also, all the localization assemblies are copied to bin/Debug eventhoug I do not need them... why is that and how do I get rid of localization assemblies? Can I just delete them?
When I checked that and chose the few assemblies I needed in my project, I discoverd that ALL the Telerik WPF assemblies have been copied to ...\lib\RCWPF\2013.2.611.40, not just the referenced assemblies as the check box stated. Also ALL the language assemblies were copied as well eventhough I do not intend to use localization.
When I build my solution now only the assemblies I referenced are copied to bin/Debug folders so why did the WPF VS Extenstion copy ALL the WPF assemblies to my solution and can I just waste my time tracking down assemblies I do not need and delete them?
Also, all the localization assemblies are copied to bin/Debug eventhoug I do not need them... why is that and how do I get rid of localization assemblies? Can I just delete them?
1 Answer, 1 is accepted
0
Hello Dean,
Thank you for contacting us!
I get your point and it make sense. The reason why we copy all assemblies is to give the user ability to manage his Telerik references using the Configure wizard. If you don't need some assemblies you can delete them but then you won't be able to add more references using the Configure wizard.
Regarding the localization assemblies we can add an option that controls whether to copy them or not. We will consider such improvement when discussing our future plans.
What gets copied to the bin folder is controlled by Visual Studio. This is just the output of your build.
Please excuse the inconvenience caused. I hope I managed to answer your questions. Should you have any future inquires don't hesitate to contact us again.
Regards,
Petar
Telerik
Thank you for contacting us!
I get your point and it make sense. The reason why we copy all assemblies is to give the user ability to manage his Telerik references using the Configure wizard. If you don't need some assemblies you can delete them but then you won't be able to add more references using the Configure wizard.
Regarding the localization assemblies we can add an option that controls whether to copy them or not. We will consider such improvement when discussing our future plans.
What gets copied to the bin folder is controlled by Visual Studio. This is just the output of your build.
Please excuse the inconvenience caused. I hope I managed to answer your questions. Should you have any future inquires don't hesitate to contact us again.
Regards,
Petar
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>