Peter Rogers
Top achievements
Rank 2
Rank 2
Peter Rogers
asked on 09 Nov 2009, 05:54 PM
Our team is making heavy use of a number of RadControls in the context of WebParts (SharePoint 2007) and have run into issues when spanning multiple RadControl versions, specifically with regard to ajaxified controls. A clear and apparent fix seems to be to update all webparts to use the latest common denominator version of the RadControls for ASP.NET AJAX.
Going forward, however, we intend to make use of the RadMenu in our global navigation for SharePoint. Since that will be present on each page and we likely will want to adopt functionality from newer releases (we haven't yet cracked open the q3 2009 controls, but likely will shortly), it will likely necessitate that we update both the navigation with the latest version of the RadMenu control and perhaps all other WebParts that make use of RadControls.
Is there a recommended upgrade path when doing a site wide upgrade of RadControls? Should we only be concerned with those WebParts that are making use of "ajaxified" WebParts or all?
Would telerik say it's best practice to use one and only one version of the controls on the same page because of potential javascript issues?
I know this is a kitchen sink kind of posting, but our team needs to start getting our heads around these issues.
Many thanks,
Peter Rogers
Senior Software Engineer
Seyfarth Shaw LLP
Going forward, however, we intend to make use of the RadMenu in our global navigation for SharePoint. Since that will be present on each page and we likely will want to adopt functionality from newer releases (we haven't yet cracked open the q3 2009 controls, but likely will shortly), it will likely necessitate that we update both the navigation with the latest version of the RadMenu control and perhaps all other WebParts that make use of RadControls.
Is there a recommended upgrade path when doing a site wide upgrade of RadControls? Should we only be concerned with those WebParts that are making use of "ajaxified" WebParts or all?
Would telerik say it's best practice to use one and only one version of the controls on the same page because of potential javascript issues?
I know this is a kitchen sink kind of posting, but our team needs to start getting our heads around these issues.
Many thanks,
Peter Rogers
Senior Software Engineer
Seyfarth Shaw LLP
1 Answer, 1 is accepted
0
Hi Peter,
Yes, it is necessary to use the very same version of all RadControls because problems occur due to same namespaces. You cannot use different versions of Telerik.Web.UI on the same page and in teh same project.
As to how to upgrade, all you should do is the following:
1) deploy the new dll in the GAC
2) change your Web.config accordingly
More information is available below:
http://www.telerik.com/help/aspnet-ajax/moss-deploying-radcontrols.html
If you encounter problems or breaking changes after the upgrade do not hesiatate to contact us again, we will be glad to help.
Greetings,
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Yes, it is necessary to use the very same version of all RadControls because problems occur due to same namespaces. You cannot use different versions of Telerik.Web.UI on the same page and in teh same project.
As to how to upgrade, all you should do is the following:
1) deploy the new dll in the GAC
2) change your Web.config accordingly
More information is available below:
http://www.telerik.com/help/aspnet-ajax/moss-deploying-radcontrols.html
If you encounter problems or breaking changes after the upgrade do not hesiatate to contact us again, we will be glad to help.
Greetings,
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.