I have a straight forward DNN application and I need to integrate a seperate ASP.NET application. The idea is that when a link is clicked in my DNN site it redirects to the ASP.NET site. However, the domain name needs to stay the same. So basically, if it was www.dnnsite.com it would become www.dnnsite.com/aspnetsite. I think this is possible but I'm trying to understand the best way to achieve it. Is it simply an IIS configuration thing and if so can it be achieved in IIS on XP?

Any help/suggestion is much appreciated!

Thanks!

You need to add the following tag around the <system.web> tag in the dotnetnuke web.config file to stop inheritance of dotnetnuke's web.config : <location path="." inheritInChildApplications="false">

I've had the same problem, I was using the IFrame module to load sub-applications from within a DotNetNuke page to easily extend the site for some custom solutions.  It worked fine in DNN4.9 when I added the inheritInChildApplications="false" in a location tag around the system.web in the config file. 

However, I recently was forced to upgrade to DNN5.0 to see if it solved some problems with the web site (which it did), but now I can't wrap the <system.web> tag in a location tag, if I do, then *every* time I log in, I get a "Critical error - Object reference not set to an instance of an object" error in the content pane of my initial page.

As soon as I remove the inheritInChildApplications fix, then I can login without seeing an error on my page, but my SubApps don't load (can't find dependencies blah blah blah).

Any ideas?