Richard, thanks for your prompt reply.
I have seen the KB Article: http://www.telerik.com/support/kb/winforms/general/ilmerge-telerik-winforms-assemblies.aspx and your video here.
As mentioned before, we are trying to go with the second approach - of merging multiple Telerik assemblies to one, and using this in our application.
We used the following commands to build the assembly PLWinFormsControls:
cd "C:\Program Files (x86)\Microsoft\ILMerge"
ilmerge /out:PLWinFormsControls.dll TelerikCommon.dll TelerikData.dll Telerik.WinControls.UI.dll Telerik.WinControls.UI.Design.dll Telerik.WinControls.dll Telerik.WinControls.GridView.dll Telerik.WinControls.Scheduler.dll Telerik.WinControls.Docking.dll Telerik.WinControls.RadChart.dll Telerik.WinControls.RadDock.dll Telerik.WinControls.RadMarkupEditor.dll
Then changed the reference from the separate Telerik dlls to PLWinFormsControls dll.
Also added the following line in Sub New()
RadTypeResolver.Instance.TypeResolverAssemblyName = "PLWinFormsControls"
While this run well in debug mode and runs fine on a test machine (without any Telerik dlls), visual studio crashes with the message "Visual Studio is attempting to load class instances from a different than the original used to create your components. This will result in failure to load your designed component." This happens when we try to load the main form in design view.
Please see the attached screenshot.
In other words we can deploy what we have, but we are unable to view (or change) the design of the form in Visual Studio, unless the references are reverted back to the different Telerik DLLs.
One thing that I didn't mention and that is different from the video (link) is that the application's main form is a RadForm. Therefore:
I am not sure if this would have anything to do with the designer problem.
I was wondering if anyone else has come across this problem?