I am moving my DNN site to a new server.  I had everything upgraded (5.6.1 and all of the modules) running on .NET 3.5 on a Server 2003 box.  I backed up the db, copied the folder and moved the instance over in the usual manner.  I set the app pool on the new server to .NET 2.0 to start and everything works fine.

When I changed the app pool to .NET 4.0, I noticed a serious performance drop.  I happened to have web.config open in VS on the server and it kept asking me to reload the changes (when there should not have been any).  Then I noticed that DNN kept "upgrading" the framework on each page load, changing web.config and causing the app to reload which caused the performance issue (changes to web.config shown below).  I realize that it should do this the first time it detects the app pool is .NET 4, but something is messed up.  I looked through the Upgrade class and I can see  TryUpgradeNETFramework() called by UpgradeToVersion_510() but I'm not seeing why this is happening.  The host page is correctly reporting the version as 5.6.1.  I've also tried setting AutoUpgrade to false, but that had no effect.

I'm at a loss here; any help is appreciated.

I followed Michael Washington's directions here
http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2619/Upgrading-DotNetNuke-to-ASP-NET-4-0.aspx


setup on the new server:
windows server 2008 x 64 (it is not R2)
IIS 7
.NET 4.0 classic app pool

snip from web.config
        <!--Upgraded by .NET 4.0 Upgrade version 5.6.1 - Date: 2/7/2011 4:10:14 PM-->
        <!--<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by .NET 4.0 Upgrade version 5.6.1 - Date: 2/7/2011 4:11:31 PM-->
        <!--<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by .NET 4.0 Upgrade version 5.6.1 - Date: 2/7/2011 4:11:43 PM-->
        <!--<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by .NET 4.0 Upgrade version 5.6.1 - Date: 2/7/2011 4:14:55 PM-->
        <!--<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />-->

 
I have a similar situation. Comments are being added to the web.config file for each page view.

But:

requestValidationMode="2.0"

Is already present. And the problem is still there. 

I'm getting 4 lines of comments added per web page visit. (Can we say OUCH?) This is added twice:

<!--Upgraded by .NET 4.0 Upgrade version 5.6.1 - Date: 3/6/2011 4:52:47 PM-->
<!--<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" xmlns="urn:schemas-microsoft-com:asm.v1" />-->

Those are in both "assemblyIdentity" nodes, i.e.:

runtime/assemblyBinding/dependentAssembly/assemblyIdentity

<assemblyIdentity name="System.Web.Extensions.Design"...
<assemblyIdentity name="System.Web.Extensions"...

But not in the Telerik node.

LOCATION NODE

I have both system.webServer and system.web wrapped in a location node as I have a subapplication running. i.e.:

<location path="" inheritInChildApplications="false">
    <system.webServer>
 ...
    </system.webServer>
    <system.web>
 ...
    </system.web>
  </location>

Removing system.web and setting:

<validation validateIntegratedModeConfiguration="true" />

Only results in an error.

I found this IIS.net forum post:

http://forums.iis.net/t/1176128.aspx

Which only confirms that this is something like what you've described above, i.e. An application is doing it (DNN). 

I cannot find anything that points me in the right direction to solve this though. 

This is show-stopper problem. 


Is there any way to work around this by modifying the web.config or something?


I could swap out the subapplication and put it under a subdomain and lose the "<location>" wrapper for the "system.web" and "system.webServer" nodes, but that's really an extremely poor solution. 

Or is there another way to get subapplications to work with DNN? 

Not sure if this helps, but these are the affected nodes that get comments added for each web page view:

     <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>