ASP.NET: Nested Web.config files in conflict
If you have a child app configured in IIS, and you don’t want the web.config of the parent application to affect your child app, here is how you tell the parent app’s config file to go chill down by the river alone.
Example:
blah.com/web.config <= Parent file
blah.com/child/web.config <= child file
Add this code around your
<location path="." inheritInChildApplications="false"> <system.web> ...whole bunch of other stuff is here already (most likely) </system.web> </location>
This will make the parent ignore the child, and not try to handle it and mess with it. Boy don’t you wish you had a parental mute button and cease and desist they couldn’t remove as a kid? That would be nice.
This does not work for ASP.NET 4.0, since the "inheritInChildApplications" attribute is not supported there anymore. Any idea how to accomplish this same thing in 4.0?