Problem:
When using RadScriptManager with EnableScriptCombine=True the controls stop working as you get a JavaScript error.
Cause: There are different reasons for this error to happen. Please, check the list below: 1) RadScriptManager was unable to correctly determine if the browser supports gzip/deflate compression; 2) A custom ScriptReference is added to RadScriptManager (having a Path property specified), which depends on the combined scripts or vice-versa; 3) There is an unfound bug in RadScriptManager;
Resolution: Below are the respective resolutions for the problems, described above: 1) Implement your own browser detection mechanism and use the OutputCompression property of RadScriptManager to control it. You might also try to reinstall the browser, or restore its initial settings; 2) Upgrade to the latest Telerik.Web.UI version. You can download it from your ClientNet account. RadScriptManager now supports the addition/insertion of custom scripts depending/dependent on other scripts. The custom script is added as a separate <script> tag and the general merged script is split respectively. 3) Check the Release notes - the problem might have already been fixed. Upgrade to the latest Telerik.Web.UI version and check if the bug is not fixed while fixing another one. Send us a small website, demonstrating the problem.
Problem:
You receive the following error even if you had already added the handler.
~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadScriptManager requires a HttpHandler registration in web.config.
Cause:
The <handlers> or <httpHandlers> sections are placed under the <location> section and RadScriptManager cannot find them.
Resolution:
Set the EnableHandlerDetection="false" property of RadScriptManager.
Problem:
There is not RadScriptManagerProxy, what should I do?
Resolution
You can use the ScriptManagerProxy. Yes, place the RadScriptManager control on the page /master page and the ScriptManagerControl on the user control / content page.
Problem:
The RadScriptManager is incompatible with the
Ajax Control Toolkit
(Version number 40412 and higher).
The following error appears when controls from the ACT are present on the page:
Microsoft JScript runtime error: AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the ToolkitScriptManager in AjaxControlToolkit.dll.
Resolution for .NET 4.0 projects:
Upgrade the RadControls for ASP.NET AJAX version 2010.1.625 or newer.
Important: Make sure you use the .NET 4.0 build of both Telerik.Web.UI.dll and AjaxControlToolkit.dll
If upgrade is not option you can use the following workaround:
CopyASPX
<telerik:RadScriptManager runat="server" EnableScriptCombine="false" />
Resolution for .NET 3.5 projects:
Override the references to MicrosoftAjax.js and MicrosoftAjaxWebForms.js to point to the ACT script files.
CopyASPX
<telerik:RadScriptManager runat="server">
<Scripts>
<asp:ScriptReference Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Name="MicrosoftAjax.js" Path="Scripts-40412/MicrosoftAjax.js" />
<asp:ScriptReference Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Name="MicrosoftAjaxWebForms.js" Path="Scripts-40412/MicrosoftAjaxWebForms.js" />
</Scripts>
</telerik:RadScriptManager>The script files are obtained by building the ACT from source. Sample project, including the scripts for version 40412, is attached.