Multiple web.config files in a virtual directory

[Raghu]

Is it possible to have multiple web.config files in a given virtual
directory in different directories? For example:

http://localhost/myapp (Virtual directory maps to C:\MyApp)
http://localhost/myapp/newFolder (web folder in the above virtual dir maps
to C:\MyApp\NewFolder)

Can I have one web.config file at C:\MyApp and another at
C:\MyApp\NewFolder? When I tried to do this, VS.NET web project (during
debugging) throws an errors saying that something is wrong at the server? So
I compiled the project and tried to bring to navigate to a page in the
browser (without debugging), I still get an error. But when I remove the
web.config file at C:\MyApp\NewFolder, it works fine.

Any help is appreciated.

Thanks.
Raghu/..

[Curt_C [MVP]]

yes, but you are limited what can be in the second one... usually thought
its better to have the ONE in the root and use the <location> tags to
explicitely handle things in the subfolders

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"Raghu" <Ra***@nospamzzzqcsi.com> wrote in message
news:ui**************@TK2MSFTNGP12.phx.gbl...

Is it possible to have multiple web.config files in a given virtual
directory in different directories? For example:

http://localhost/myapp (Virtual directory maps to C:\MyApp)
http://localhost/myapp/newFolder (web folder in the above virtual dir maps
to C:\MyApp\NewFolder)

Can I have one web.config file at C:\MyApp and another at
C:\MyApp\NewFolder? When I tried to do this, VS.NET web project (during
debugging) throws an errors saying that something is wrong at the server? So I compiled the project and tried to bring to navigate to a page in the
browser (without debugging), I still get an error. But when I remove the
web.config file at C:\MyApp\NewFolder, it works fine.

Any help is appreciated.

Thanks.
Raghu/..

[John Saunders]

"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl...

yes, but you are limited what can be in the second one... usually thought
its better to have the ONE in the root and use the <location> tags to
explicitely handle things in the subfolders

Curt, what are the limitations on the web.config in the subfolder?

The only limitation I'm aware of is an issue with assembly references if the
sub-folder is also an application. If the main web.config uses

<httpModules>
<add name="MyModule" type="MyNamespace.MyModule, MyAssembly" />
</httpModules>

Then the subapplication will be looking for a SubApp\bin\MyAssembly.dll. You
can add a <remove name="MyModule" /> to the sub-web.config, but it's already
too late - ASP.NET will be looking for MyAssembly.dll before it gets around
to processing your <remove>. The workaround is to place a dummy
MyAssembly.dll in SubApp\bin.
--
John Saunders
johnwsaundersiii at hotmail

[Curt_C [MVP]]

Are you saying the SUB is flagged as an APP in VS?

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"John Saunders" <jo**************@notcoldmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl...

yes, but you are limited what can be in the second one... usually thought its better to have the ONE in the root and use the <location> tags to
explicitely handle things in the subfolders
Curt, what are the limitations on the web.config in the subfolder?

The only limitation I'm aware of is an issue with assembly references if

the sub-folder is also an application. If the main web.config uses

<httpModules>
<add name="MyModule" type="MyNamespace.MyModule, MyAssembly" />
</httpModules>

Then the subapplication will be looking for a SubApp\bin\MyAssembly.dll. You can add a <remove name="MyModule" /> to the sub-web.config, but it's already too late - ASP.NET will be looking for MyAssembly.dll before it gets around to processing your <remove>. The workaround is to place a dummy
MyAssembly.dll in SubApp\bin.
--
John Saunders
johnwsaundersiii at hotmail

[Curt_C [MVP]]

oopss... I mean IIS, not VS

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"John Saunders" <jo**************@notcoldmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl...

yes, but you are limited what can be in the second one... usually thought its better to have the ONE in the root and use the <location> tags to
explicitely handle things in the subfolders
Curt, what are the limitations on the web.config in the subfolder?

The only limitation I'm aware of is an issue with assembly references if

the sub-folder is also an application. If the main web.config uses

<httpModules>
<add name="MyModule" type="MyNamespace.MyModule, MyAssembly" />
</httpModules>

Then the subapplication will be looking for a SubApp\bin\MyAssembly.dll. You can add a <remove name="MyModule" /> to the sub-web.config, but it's already too late - ASP.NET will be looking for MyAssembly.dll before it gets around to processing your <remove>. The workaround is to place a dummy
MyAssembly.dll in SubApp\bin.
--
John Saunders
johnwsaundersiii at hotmail

[John Saunders]

I meant _if_ the sub is flagged as an app. The issue I raised only happens
if the sub is an app.
--
John Saunders
johnwsaundersiii at hotmail
"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...

oopss... I mean IIS, not VS

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"John Saunders" <jo**************@notcoldmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl...

yes, but you are limited what can be in the second one... usually thought its better to have the ONE in the root and use the <location> tags to
explicitely handle things in the subfolders

Curt, what are the limitations on the web.config in the subfolder?

The only limitation I'm aware of is an issue with assembly references if

the

sub-folder is also an application. If the main web.config uses

<httpModules>
<add name="MyModule" type="MyNamespace.MyModule, MyAssembly" />
</httpModules>

Then the subapplication will be looking for a SubApp\bin\MyAssembly.dll.

You

can add a <remove name="MyModule" /> to the sub-web.config, but it's

already

too late - ASP.NET will be looking for MyAssembly.dll before it gets

around

to processing your <remove>. The workaround is to place a dummy
MyAssembly.dll in SubApp\bin.
--
John Saunders
johnwsaundersiii at hotmail

[Curt_C [MVP]]

Ah, yes. IF it's an "app" then all bets are off.
If it's not there are some things, like the security model/type that can't
be "re-set" in a sub web.config, only once in the root one.

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"John Saunders" <jo**************@notcoldmail.com> wrote in message
news:O5*************@TK2MSFTNGP10.phx.gbl...

I meant _if_ the sub is flagged as an app. The issue I raised only happens
if the sub is an app.
--
John Saunders
johnwsaundersiii at hotmail
"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...

oopss... I mean IIS, not VS

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"John Saunders" <jo**************@notcoldmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl...
> yes, but you are limited what can be in the second one... usually

thought

> its better to have the ONE in the root and use the <location> tags to > explicitely handle things in the subfolders

Curt, what are the limitations on the web.config in the subfolder?

The only limitation I'm aware of is an issue with assembly references

if the

sub-folder is also an application. If the main web.config uses

<httpModules>
<add name="MyModule" type="MyNamespace.MyModule, MyAssembly" />
</httpModules>

Then the subapplication will be looking for a

SubApp\bin\MyAssembly.dll. You

can add a <remove name="MyModule" /> to the sub-web.config, but it's

already

too late - ASP.NET will be looking for MyAssembly.dll before it gets

around

to processing your <remove>. The workaround is to place a dummy
MyAssembly.dll in SubApp\bin.
--
John Saunders
johnwsaundersiii at hotmail