RadScriptManager & SharePoint 2013

[Daniel]

Hi, we're trying to use the ASP.NET AJAX controls in our SharePoint pages as visual web parts. We've only used the RadGrid, RadComboBox & RadAjaxManager and they seem to work for the most part. We're trying to incorporate the RadScriptManager as well. We can't add it inside the web part as SharePoint throws the error "Only one instance of a ScriptManager can be added to the page". Which makes sense as the MasterPage (seattle.master) uses a ScriptManager. So, we've tried removing the ScriptManager and replace it with RadScriptManager like:

<!--SPM:<asp:ScriptManager id="ScriptManager" runat="server" EnablePageMethods="false" EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true"/>-->

to

<!--SPM:<telerik:RadScriptManager ID="RadScriptManager1" runat="server" EnablePageMethods="false" EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true"/>-->

 

The <!--SPM:--> tag is used in the seattle.html because MS don't recommend you edit the seattle.master file directly in SharePoint 2013. But it throws the same error "Only one instance of a ScriptManager can be added to the page" in the ULS logs. It's like SharePoint is ignoring the RadScriptManager control.

 

Any thoughts?

 

We're using version 2018.1.117.40 of the ASP.NET AJAX controls and SharePoint 2013 (15.0.4569.1000) with the latest patches as at 2018/02/16.

[Vessy]

Hi Daniel,

You can try replacing the ScriptManager with RadScriptManager in the way described by my collegue here:
https://www.telerik.com/forums/replacing-scriptmanager-with-radscriptmanager-from-webpart-dynamically---error#G4PiPdl-BEKzHxg7p7bX3w

You have to make sure that all configurations mandatory for RadScriptManager are applied to the site (e.g. to register its handlers):
https://docs.telerik.com/devtools/aspnet-ajax/sharepoint/2007/create-an-ajax-enabled-sharepoint-webpart-that-uses-the-telerik-controls

Regards,
Vessy
Progress Telerik

[Daniel]

Thanks for the links. The above approaches seem to work with SharePoint 2010 but not 2013. I think we'll leave it for the moment as all the controls we've used seem to be working okay.

[Vessy]

Hi,

Thank you for the update, Daniel - I am glad you have found a solution that is applicable for your scenario at the moment. Let us know if you need our assistance should you decide o chnage that in the future.

Regards,
Vessy
Progress Telerik