There are only three modifications made to web.config when switching to ASP.Net 4.0 so these can easily be made manually. The automatic update to web.config using the XmlMerge capability can fail in some cases such as if the ASP.Net worker process account does not have sufficient permissions on the root folder of the website, if web.config is read-only, or if a <location . . > section is used in the web.config.

Here are the three changes:

1. The attribute/value requestValidationMode="2.0" is added to the <httpRuntime . . . /> node.

2. The <bindingRedirect . . . /> for System.Web.Extensions is changed to the following:

<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion-"4.0.0.0" />

3. The <bindingRedirect . . . /> for System.Web.Extensions.Design is changed to the following:

<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion-"4.0.0.0" />

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

I'm glad that that fixed it for you! And thanks for the offer of a beer.

I would be interested to know, however, if your web.config file includes a <location> section as that may be one of the key causes of the XmlMerge filing to update the web.config for ASP.Net 4.0.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner