Yes, the CFMX7 installation documents indicate that CFMX7 can co-exist with
cfmx6.x and previous versions. You can install it to run using its own
internal webserver running on port 8500 or 8501, typically. You can also
create a virual webserver and configure cfmx7 to use it while cfmx6 runs on
your other site(s).
Nathan Drury - 31 May 2006 02:37 GMT
Thanks for your reply Ken.
We use IIS as our standard web server, so to maintain consistency we'd prefer
to use it instead of the built in CF web server. I don't know a great deal
about virtual servers in IIS, so can you tell me what would I need to do to set
up IIS and/or CF so that a particular site (eg. <a target=_blank
class=ftalternatingbarlinklarge href="http://abc)">http://abc)</a> would know
to use CF 7 rather than CF 6? I don't want the users to have to add the port
number to the URL, so if I create an IIS virtual server following these
guidelines (<a target=_blank class=ftalternatingbarlinklarge
href="http://support.microsoft.com/default.aspx?scid=kb;en-us;816576)">http://su
pport.microsoft.com/default.aspx?scid=kb;en-us;816576)</a> with a port
different to port 80, will the port have to be added to the URL (eg. <a
target=_blank class=ftalternatingbarlinklarge href="http://abc:8080)?
In">http://abc:8080)?
In</a> a nutshell, what I'm after is one site such as <a target=_blank
class=ftalternatingbarlinklarge href="http://abc1">http://abc1</a> to use CF 6
and another such as <a target=_blank class=ftalternatingbarlinklarge
href="http://abc2">http://abc2</a> to use CF 7.
Cheers
Nathan
PS - sorry about the multiple posts. I wasn't sure where was the best place
to put it.