I've recently upgraded to DNN 5.0.0, and am on a shared host.  To extend functionality for custom situations, I've created a small sub-application in a folder underneath of my DNN root that is configured as an ASP .NET application.  I can then include IFrame modules in my DNN pages to load the custom pages to have any functionality needed within the DNN portal.

Problem is, because of inherited web.config files, the DNN root's web.config is inherited by the sub-application and breaks the sub-application.  The only way I could get it to work (with DNN 4.9) was to put a <location path="." inheritInChildApplications="false"> tag around the <system.web> in the DNN web.config.  This worked magically.

Now that I've upgraded to DNN 5.0.0, this <location> tag wrapper isn't so magical.  It took awhile for me to figure out that it was the cause of a "Exception Error - Object Reference Not Set To An Instance of an Object" message popping up in the content pane of the first page that is loaded after a user successfully logs in.  As soon as I take out the <location> tag, the error doesn't pop up after a log in, but my sub-application no longer works.

Because of the hosting situation, I don't have the ability to move my DNN installation into a sub-application so that it's not the root (my portal address would become www.mywebsite.com/dnn or whatever).  I also don't have the option of moving my other sub-application so that it's not under the dnn application.  I'm basically stuck as far as I can tell in terms of the heirarchy.

Anyone know why the inheritInChildApplications attribute breaks DNN 5.0.0's login?  Anyone know of any other solution to allow a nested asp .net application with DNN?