Directory / Application question for Web dotNet

[Tom]

Ok, the scenario is this: A planned ASP .Net website will
have a directory called "Reports". However there are
multiple such reports and the developers will be working
quasi-independently on separate report applications. They
would prefer not to we working on the same
Project/Solution in VS.Net. So once each report
application is created and compiled separately. They will
be moved to the web server into sub-directories off of the
Reports directory. The rub is that each such directory
will need to be created as a separate "application" under
IIS.

Now, the question is this: Is there any way that this can
be configured (in the scenario described above) where only
the "Reports" directory needs to be an "Application" under
IIS? or are we forced to make each directory under Reports
an IIS Application?

Its not a huge issue, but if we can do this it will make
our deployment easier by keeping us from having to touch
each web server to create a new virtual
directory "Application" each time these guys create a new
report.

TIA,
Tom

[Michael Giagnocavo [MVP]]

Yes it's possible, with some things to consider:

Some web.config settings will not work

You will need to add options to the web.config to search /reportX/bin/
for assemblies, or, copy the /reportX/bin to /bin.

-mike
MVP

"Tom" <To*@TheEnderles.org> wrote in message
news:09****************************@phx.gbl...

Ok, the scenario is this: A planned ASP .Net website will
have a directory called "Reports". However there are
multiple such reports and the developers will be working
quasi-independently on separate report applications. They
would prefer not to we working on the same
Project/Solution in VS.Net. So once each report
application is created and compiled separately. They will
be moved to the web server into sub-directories off of the
Reports directory. The rub is that each such directory
will need to be created as a separate "application" under
IIS.

Now, the question is this: Is there any way that this can
be configured (in the scenario described above) where only
the "Reports" directory needs to be an "Application" under
IIS? or are we forced to make each directory under Reports
an IIS Application?

Its not a huge issue, but if we can do this it will make
our deployment easier by keeping us from having to touch
each web server to create a new virtual
directory "Application" each time these guys create a new
report.

TIA,
Tom