Hi
Regarding 'Redistributing Telerik RadControls for Winforms' discussed here, we are building Telerik assemblies from source code using the OEM conditional symbol approach with our application assembly name specified in OemAssemblyName in RadControl.cs. This is to protect Telerik controls in our distribution. This seems to work fine in that unauthorised applications get the trial version pop-up whereas the authorised one doesn't.
My question: Can you advise the best way (or what needs to be done) to create an 'installer' which can be used to register the source build assemblies for design time use in Visual Studio 2010 (i.e. to create/populate a Visual Studio Toolbox tab and to register assemblies for design-time support)?
The reason: Our solution is structured so that Telerik assemblies are copied to an ExternalDlls folder and projects referencing Tererik point to assemblies in ExternalDlls. If Telerik UI controls are not installed on my development PC then I don't have Visual Studio design capabilities. However, if I install either the full licensed or Trial versions of Telerik controls (NOT the assemblies built from source) then I get all sorts of conflicts because the assemblies in ExternalDlls (built from source) and assemblies from install versions have different public key tokens.
Hope this question makes sense. Any advice will be greatly appreciated.
Regards
Shaun
Regarding 'Redistributing Telerik RadControls for Winforms' discussed here, we are building Telerik assemblies from source code using the OEM conditional symbol approach with our application assembly name specified in OemAssemblyName in RadControl.cs. This is to protect Telerik controls in our distribution. This seems to work fine in that unauthorised applications get the trial version pop-up whereas the authorised one doesn't.
My question: Can you advise the best way (or what needs to be done) to create an 'installer' which can be used to register the source build assemblies for design time use in Visual Studio 2010 (i.e. to create/populate a Visual Studio Toolbox tab and to register assemblies for design-time support)?
The reason: Our solution is structured so that Telerik assemblies are copied to an ExternalDlls folder and projects referencing Tererik point to assemblies in ExternalDlls. If Telerik UI controls are not installed on my development PC then I don't have Visual Studio design capabilities. However, if I install either the full licensed or Trial versions of Telerik controls (NOT the assemblies built from source) then I get all sorts of conflicts because the assemblies in ExternalDlls (built from source) and assemblies from install versions have different public key tokens.
Hope this question makes sense. Any advice will be greatly appreciated.
Regards
Shaun