method get_EnableCdn in type system.web.ui.scriptmanager from assembly system.web.extensions, version=3.5.0.0, 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="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
6 </dependentAssembly>
7 <dependentAssembly>
8 <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
9 <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
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">
2
2
More Info:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/236690-error-rendering-control.aspx
http://forums.asp.net/p/1497738/3661536.aspx
Thanks, Kathy,
ReplyDeleteyou made my day..
appliesTo="v2.0.50727" is a life saver.
Thanks,
Amit
Thank you so much. Just spent 2 days beating my head on this one.
ReplyDeleteAdding 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
Thank you very much...
ReplyDeleteYou solve my biggest problem...
This appliesTo="v2.0.50727" works..
Terrific! Thank you so much for that.
ReplyDeleteI had just migrated to a new server and the "appliesTo..." was also the key for me.
This article was helpful, thank you.
ReplyDeletevery interesting and easy solution. worked for me!.
ReplyDeleteThx that helped a lot
ReplyDeleteThis 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.
ReplyDelete