I want to have 2 completely separate instances of my ASP/Access application
running on the same web server. One will be a live production application,
and the other part of a system test environment to check out code/database
changes etc prior to deploying them on the live system.
The appln code is in a virtual directory so the name of this is hard coded
in most of the ASP pages where I do the #includes and elsewhere. It seemed
like a good idea at the time, to make the application more portable. Now I'm
not so sure... I seem to need 2 virtual directories with the same name.
Maybe I'm going off in the wrong direction altogether with these virtual
directories.
I'm trying to understand the IIS concept of Web site Vs. virtual direcory: I
can't find anything that gives a conceptual description: just which boxes to
tick in which Windows screens, or what to do when it goes wrong. I need an
overview to help me understand what the options are, and the pros and cons
of each option.
(The appln uses an Access database but that's no problem as I store the DB
filename in an Application variable. It can easily be changed by editing the
respective global.asa files.)
I've Googled and searched MSN all day and I just can't get a handle on how
to do this. Can somebody point me in the right direction?
MightyC
It it's relevant I'm using IIS 5 / Windows XP Pro
(Previously posted on microsoft.public.inetserver.iis.activeserverpages but
no answer.)
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.536 / Virus Database: 331 - Release Date: 03/11/03