ASP.NET web.config inheritance 1.1 child vs 2.0 child

Is there a way to prevent a ASP.NET 1.1 child application from inheriting a web.config from the parent?  Our main root application is 2.0.  We have settings in that web.config for 2.0 that is not recognized in 1.1.  So we want child 2.0 applications to inherit these settings but NOT 1.1 child applications since they don't recognize them.  Any idea how to do this?
ibidataAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
taliesin1977Commented:
I have seen other blogs indicating that the property "inheritInChildApplications" is only support for .NET 2.0 and later and will cause an exception with the .NET 1.1 application reads it.

Perhaps you can use a combination of <location> and the <clear /> command to just clear out the sections you don't need in your child application...Also though, could you not just override the offending sections in the child app's web.config to a 1.1 compliant format?
0
 
ibidataAuthor Commented:
I've added the <system.webServer> section to the root web.config because other 2.0 child applications need it.  However, this section causes a server error in child 1.1 applications.  How do I hide or disable this section from child 1.1 applications?

Doing this in the child 1.1 web.config causes the same error:

<system.webServer>
      <clear/>
</system.webServer>
0
 
nmarunCommented:
Please accept your solution and mark this issue for PAQ.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.