Monday, June 21, 2010

RadScriptManager strange error : method get_EnableCdn ...

The error:

method get_EnableCdn in type system.web.ui.scriptmanager from assembly system.web.extensions, version=, culture=neutral PublicKeyToken=31bf3856ad364e35' does not have an implementation.

The solution:

1. Delete this line from the pages you have it:

1 <%@ Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %>

2. Verify this section in your web config:

1 <runtime>
2 <assemblyBinding appliesTo="v2.0.50727" xmlns="urn:schemas-microsoft-com:asm.v1">

3 <dependentAssembly>

4 <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>

5 <bindingRedirect oldVersion="" newVersion=""/>

6 </dependentAssembly>

7 <dependentAssembly>

8 <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>

9 <bindingRedirect oldVersion="" newVersion=""/>

10 </dependentAssembly>

11 </assemblyBinding>

12 </runtime>

Very important: Make sure you use the: appiesTo in the following line:

1 <assemblyBinding appliesTo="v2.0.50727" xmlns="urn:schemas-microsoft-com:asm.v1">

3. If the error message remains or in the case you were not able to see your telerik controls in design mode (you have a very big an strange error instead of it), you could also try:
- Make sure you have Telerik.Web.UI.dll, Telerik.Web.Design.dll and Telerik.Web.UI.xml in your bin folder.

4. Verify that you have only one reference to System.Web.Extensions in your project (whether you have it in your bin folder or in your GAC)

More Info:


  1. Thanks, Kathy,
    you made my day..
    appliesTo="v2.0.50727" is a life saver.


  2. Thank you so much. Just spent 2 days beating my head on this one.
    Adding the 'appliesTo="v2.0.50727"' was the ticket.
    I think it started after I tried to upgrade my application to target .Net 4, then decided to go back to .Net 2.0.

    Thanks again... Terry

  3. Thank you very much...
    You solve my biggest problem...
    This appliesTo="v2.0.50727" works..

  4. Terrific! Thank you so much for that.
    I had just migrated to a new server and the "appliesTo..." was also the key for me.

  5. This article was helpful, thank you.

  6. very interesting and easy solution. worked for me!.

  7. Thx that helped a lot

  8. This helped me when I was getting this error on a 3.5 project I had to takeover. It had liberal use of scriptmanager and kept giving this error. Simply removing double references to System.Web.Extension and adding the appliesTo="v2.0.50727" fixed it.