Help with recursive web.config files.

[Nathon]

I have a .NET web app (.NET Nuke) and then I have a virtual directory under
that app with a completely independent .NET web app. However, I get the
following error when executing the second web app.

"An error occurred during the processing of a configuration file required to
service this request. Please review the specific error details below and
modify your configuration file appropriately."

Then the last function to be executed is
"DotNetNuke.HttpModules.UrlRewrite". How do I forgo the .NET Nuke web.config
and have the lower app just use it's own web.config? It's setup as follows.

Logical Layout:
http://www.daltondirect.com (.NETNuke) (upper app)
http://www.daltondirect.com/apps/URLCodec (URL Coder/Decoder) (lower app)

Physical Layout:
Drive:\DaltonDirect\ (upper app)
Drive:\Apps\UrlCodec\ (lower app)

--
Nathon Dalton
Owner
Dalton Direct

[vatekman]

It looks like that is the way that MS wants it to happen.... Read their article about inheritance of settings in the web.config file here

I ran into the same problem, and MS should have listed on that page if there is a way to prevent the processing of parent web.config files. I know that quite often with creating web apps, I might ahve a master application and then other applications in sub-directories and I do not always want to use the same tools... In my case, it is an error that occured because I needed a specific program provider included in my main app, but I do not need it in any other app...

Done ranting... Hopefully there will be a way around this...

-Matt

PS - In my case, I needed the editor on a page that was in a subdirectory, so I created a web.config in the directory with the editor I needed and added just that one line and removed the line from the web.config in my root directory. That seems to make all my apps happy, but it does not really make me happy... I thought that was the whole reason to make directories in IIS as applications, so that it would know not to go down the tree...