Geek Answers Handbook

Creating .NET 3.0 Sub-Applications in .NET 1.1 Applications in IIS / ASP.Net

I'm basically trying to do the same thing as this question , create a new application in the folder so that it can be obtained as follows.

* http://www.domain.com/ < Main App
* http://www.domain.com/newapp < New App

The problem is that newapp reads web.config from the main application, which causes errors because it does not have the same DLLs, etc.
For a new application in IIS, the starting point is set to / newapp, so I'm not sure why it reads web.config from / at all. It is installed as a native application.

I am testing this in IIS6 on XP Pro, so I'm not sure if that matters. The main application is dotnet 1.1, and the new application is 3.0.

Edit: Adding 'inheritInChildApplications to <location> does not work in 1.1, you get an error:

Parser Error Message: Unrecognized attribute 'inheritInChildApplications'
+5
source share
2 answers

This is by design. Web.config is read from the root to the appropriate application folder. All changes in the root apply to your application, unless your application changes it. Read this MSDN link to better understand the hierarchy and inheritance of Web.config.

In order for your application to ignore the settings in the root directory, you need to use the location element with the inheritInChildApplications attribute set to false for the path.

Sort of:

<location path="." inheritInChildApplications="false">
 <settings.....>
</location

, web.config, , . "." , , .

+4

- inheritInChildApplications .net 1.1.

, , . , 1.1.

, - 2.0 , inheritInChildApplications:

0

More articles:


All Articles