Geeks With Blogs
Bunch's Blog One day I'll have a catchy subtitle, one day

This trick might work if you have an application that has been moved from the 2.0 framework to 3.5. This happened to me recently and I had tried removing the Web.Extensions reference and adding it back in, deleting old pages that had the older ScriptManager on them and manually removing then adding back the Web.Extensions sections in the web.config file. Nothing worked so I compared the web.config files from the problem project to one that was created from scratch targeting the 3.5 framework.

I saw that on the updated project the <configuration> tag looked like:

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

where the fresh project was just <configuration>. Once I removed the xmlns=http://schemas.microsoft.com/.NetConfiguration/v2.0 the project would compile and run again.

Technorati Tags: ,
Posted on Monday, November 16, 2009 6:32 AM | Back to top


Comments on this post: ScriptManager is Ambiguous

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Bunch | Powered by: GeeksWithBlogs.net