6/5/2009 1:00 PM
We are in the process of deploying a new corporate website with DotNetNuke as our back-end content management system. After I installed DotNetNuke, I wanted to install two additional applications underneath the DotNetNuke install. However, once I configured the applications in IIS7, I was unable to browse to either application due to a known ASP.NET bug, whereas web.config files cascade down so the application/virtual directory site is still loading the root DotNetNuke web.config file.
After searching the Internet, and with a bit of trial and error, I was able to successfully get both applications to run correctly by updating each of the application’s web.config files with the following:
Validated with IIS 7, SQL Server 2005, and DotNetNuke version 4.9.4.
1 comment(s) so far...
By Robert BRavery on
12/4/2011 2:20 PM
Re: How to install additional applications / virtual directories under a root DotNetNuke installation
Great help. You can't believe I had this exact problem this weekend. Took me hours to figure it out.. I eventually did what you suggested and removed the handlers and modules. Works great now.
Should I also remove the name spaces? Is there merit in that.