Web.config conflicts with multiple web applications

[cliffnelson]

background

I have a hosting account with an ASP.NET 2.0 application with web.config at the root level,

I have added DotNetNuke in a subdirectory that has been installed as an application via control panel and has a web.config in the subdirectory.

If web.config at the root level is present, the root level app runs fine, but DotNettNuke fails with web.config compile errors,

If I remove (rename) web.config at the root level, DotNetNuke sees its web.config file and runs fine.

the parse error message is always referring to the same location

E:\web\myhealthweb\htdocs\web.config

regardless of which web.config is actually in play.

How can I configure the system to see each web.config correctly?

thx,

Cliff Nelson

[wisemx]

This can be a real nightmare, its known as web.config inheritance.

http://www.kowitz.net/archive/2007/05/16/stopping-asp.net-web.config-inheritance.aspx

[cliffnelson]

You are most definitely the man,

very easy solution, back up and running.

many thanks,
Cliff Nelson

[wisemx]

Cool. I do try my best to help. http://community.discountasp.net/emoticons/wink.gif

[bruce]

Interesting.. didn't know that.

I know this will work on IIS7 for sure. I wonder if it works for IIS6.

Bruce

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)