Telerik assemblies needs to be rebuild with a specific key in some redistribution scenarios, so that the assemblies can be bound only to a single WPF application. This is described in the following article: https://docs.telerik.com/devtools/wpf/licensing/protecting-telerik-assembly
Currently, to protect the dlls you need to rebuild the entire source code of Telerik UI for WPF. Sometimes this is not very convenient and it is prompt to errors because several steps should be followed and also few prerequisites should be met.
Consider providing a new mechanism to protect the Telerik assemblies, which is more convenient and gives better protection.
Hello Pierre-Yann,
Thank you for the extra feedback.
Regards,
Martin Ivanov
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
New mechanism should be compatible with nuget, ideally even with public nuget.org
Another vendor is doing this scheme:
AddLicense("license_code");
This works fine with WPF and WinForms packages. The only specific task that licensed dev must do after changing of version via nuget is to set the new license_code.
As the license_code will be lost in the middle of the software binaries, it will a lot more difficult for a third party to get it than current Telerik WPF mechanism.