Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Inheritance disaster! DNN 5.6.1 in root, .net 2 app in subfolderInheritance disaster! DNN 5.6.1 in root, .net 2 app in subfolder
Previous
 
Next
New Post
2/16/2011 8:23 AM
 
m . . .

In your case, I suspect that the web.config modifications had already been successfully made for ASP.Net 4.0 before you added the <location . . .> element. Unfortunately, other than a core code change or removing the <location . . .> element I don't see any way to completely resolve the issue. You can stop the growth of web.config and the resultant impact on performance caused by application re-starts each time web.config is modified by deleting (or renaming) the file \install\config\Net40.config. The current code will still fail to detect that the changes for .Net 4.0 have already been made and log a host alert error in the Event Viewer each time so you'll need to watch that the event log does not grow overly large and clear it as needed.

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
 
New Post
2/16/2011 12:33 PM
 
Thanks Bill, 
I am going to downgrade this site to .net 3.5

For my future reference (and for others):

To upgrade to ASP.NET 4.0, upgrade DNN framework, upgrade modules, install modules.


Do the following:

1. Backup the web.config
2. In web.config Remove the location tag above <system.webServer>
3. In web.config Remove the location closing tag below </system.web>

4. Upgrade to DNN framework that has this issue resolved (backup the httpdocs folder and DNN database before upgrading):
http://www.dotnetnuke.com/Resources/Forums/tabid/795/forumid/108/threadid/407924/scope/posts/Default.aspx

Thread title: Re: Inheritance disaster! DNN 5.6.1 in root, .net 2 app in subfolder

(should be GREATER THAN DNN 5.6.1)

5. Install any modules you want to upgrade / install; 
then BACKUP the DNN httpdocs folder and database AGAIN into the private directory

6. Upgrade the ASP.NET version to 4.0 at host

7. Check the event log to make sure the site has auto-upgraded to .net 4

8. In web.config replace the location tags:

<location path="." inheritInChildApplications="false"> 

goes right above <system.webServer>
_____________


</location>

tag goes below </system.web>
 
New Post
2/16/2011 4:23 PM
 
I'm having the same problem. I need the <location ...> wrapping also the <system.web> because of child apps and my web.config keeps growing even if all the changes for .Net 4.0 are already there. When can we expect a fix to this severe issue? Or should I try 3.5 for the time being?
 
New Post
2/21/2011 12:59 PM
 
I luckily had a copy of the site prior to upgrading to .net 4 and installing Razor Host

I downgraded to ASP.NET 3.5... and the site is working.  I don't plan on upgrading again till this error's fixed...
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Inheritance disaster! DNN 5.6.1 in root, .net 2 app in subfolderInheritance disaster! DNN 5.6.1 in root, .net 2 app in subfolder


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out