Last post Sep 11, 2012 04:10 AM by compositespar
Sep 10, 2012 01:16 PM|compositespar|LINK
I've searched for an answer to my issue and although I've found some things to try, I'm still not having luck with getting my setup to run.
I have the following site structure and trying to get it to run under IIS 6:
Parent Application (Web Application Project in VS). Compiled as .NET 4.0 running under dedicted app pool as .NET 4.0 in IIS 6.
- Child Application (Web Site Project in VS) set as a Virtual Directory under Parent App. This Virtual Directory (application) is set to run under its own dedicated app pool as .NET 3.5 (2.0) in IIS 6. This Child App contains legacy DLLs that have
to run under .NET 3.5.
Separately, each application runs just fine on the server, but it's the nesting within the site structure that's causing problems.
I apologize if this has been answered elsewhere and I'm just not able to search for it properly. I appreciate any and all help!
Sep 10, 2012 03:20 PM|DarrellNorton|LINK
The problems are likely due to web.config inheritance.
You can try to disable inheritance like this:
<location path="." inheritInChildApplications="false">
<compilation debug="false" />
<!-- other configuration attributes -->
You can find out more about web.config inheritance here: http://msdn.microsoft.com/en-us/library/ms178685(v=VS.100).aspx
Sep 11, 2012 04:10 AM|compositespar|LINK
Thanks for your reply Darrell!
I had wrapped the 4.0 specific tags (system.web and system.web.extensions) with a location tag (like you show) in the parent app's web config file. For some reason the 3.5 (2.0) application still generates an error for the system.web.extensions tag, even
though I have it wrapped exactly the same way in the parent app's web config file and with the proper closing tag in the right place.
I get an "Unrecognized configuration element system.web.extensions" error even with the above in place.
I appreciate your help. Thanks!