22 Aug 2012
26 Apr 2007
Link to this post
I read a thread in the Sitefinity3.0 RC forum about using the assembly redirection of Microsoft.Net to allow us to upgrade the RadControls to the later versions. Although I follow this approach, my concern is when you restructure the new controls and Sitefinity is programmed to work with the older syntax. An example would be the RadWindow. If I were to use the assembly redirection to upgrade the RadWindow, Sitefinity would then have problems as the RadWindow is used throughout the application. How would we be able to upgrade the controls that Sitefinity uses without destroying Sitefinity?
I understand that we are all moving forward with Sitefinity, but we have many sites that are still using the older version of Sitefinity. While it would be nice to upgrade them all to the latest and greatest, it is not an easy task when you have custom controls built in an older version. We have had to upgrade many controls on older sites because of bugs/limitations we have found in older RadControls. But there have been times that we have not been able to upgrade a control because of the dependence of Sitefinity itself. I hope you can find the time to give some guidance on your older versions as we are all eagerly awaiting the latest and greatest.