Hello,
We have followed the recommendation from http://www.telerik.com/help/winforms/installation-deployment-and-distribution-redestributing-telerik-radcontrols-for-windows.html and merged all the required Telerik WinControls DLLs into one assembly using ILMerge.
Now the problem is that as soon as we change the references in our Visual Studio 2010 project from the Telelerik.WinControls.*.dlls to the merged assembly, the designer view of the form fails to load and crashes Visual Studio 2010. If the designer view is not loaded, we can run in debug mode, etc and there are no problems with the resulting application deployed with the merged assembly.
I do believe that perhaps starting developing a radForm from scratch using the controls from the merged assembly (rather than the Telerik DLLs) would probably have solved this issue. But we are too far into our development to strip away everything and start designing the forms from scratch.
I was wondering if anyone else has come across this? If so, do we have a way of fixing this?
We are using WinControls version 2010.2.10.806 with Visual Studio 2010.
Regards.
We have followed the recommendation from http://www.telerik.com/help/winforms/installation-deployment-and-distribution-redestributing-telerik-radcontrols-for-windows.html and merged all the required Telerik WinControls DLLs into one assembly using ILMerge.
Now the problem is that as soon as we change the references in our Visual Studio 2010 project from the Telelerik.WinControls.*.dlls to the merged assembly, the designer view of the form fails to load and crashes Visual Studio 2010. If the designer view is not loaded, we can run in debug mode, etc and there are no problems with the resulting application deployed with the merged assembly.
I do believe that perhaps starting developing a radForm from scratch using the controls from the merged assembly (rather than the Telerik DLLs) would probably have solved this issue. But we are too far into our development to strip away everything and start designing the forms from scratch.
I was wondering if anyone else has come across this? If so, do we have a way of fixing this?
We are using WinControls version 2010.2.10.806 with Visual Studio 2010.
Regards.