Another possibility that might make a bit more sense if the component is not
changing (aka in development) is registering it with the GAC.
This can be extremely useful for registering components in a multi-user ,
multi-domain web hosting / application hosting environment.
"Albert Pascual" <Al***********@discussions.microsoft.com> wrote in message
news:0A**********************************@microsof t.com...
I have many different IIS domains running in the same directory. So you can
access that directory using mydomain1.com or mydomain2.com etc... It's the
same directory in the hard disk. Also you can access that directory using
mydomain3.com/directory
ISS handles well that way.
"dph" wrote:
I have an asp.net application that I need to run from multiple
different virtual directories. However, I don't want simply copy an
instance of the application into each of these directories as that
would be a maintenance nightmare. Also, each of these directories will
need to have a separate copy of the web.config. I was hoping it would
be as simple as a Server.Execute in a default page within each virtual
directory that loaded the shared application, but this doesn't appear
to work. The url also needs to remain the same for each virtual
directory when executing the application. Any help would be greatly
appreciated.
Thanks
