The only way is to run multiple instances of CF, or run multiple OS'es
with something like vmware.

The reason that this is difficult is because it's a bad idea. You could
easily bring down a box during development, and in your current setup
that means your production app goes down too.

It's always a good idea to develop locally. You should also stage your
development for QA on a separate box than production.

-Dave

>>> [EMAIL PROTECTED] 8/25/2005 7:46:55 AM >>>
Hi,
 I have a live site and a development site, which I use to test and
build 
any fixes for the live site. Both of them are on the same server. Now
I'm 
using components with the full address when I'm invoking them for
example:
 <cfinvoke component="MyApp.cfc.MyComponent">
 But when I'm in the development version I have to change the invoke 
statement to:
 <cfinvoke component="MyDevApp.cfc.MyComponent">
 Is there any better way to have the two versions running on the same 
server, using different sets of components, so I don't have to change
all 
the cfinvoke calls?
 Thanks
 Stephen



----------------------------------------------------------

You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject
of the email.



CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).



CFCDev is supported by New Atlanta, makers of BlueDragon

http://www.newatlanta.com/products/bluedragon/index.cfm 



An archive of the CFCDev list is available at
www.mail-archive.com/[email protected] 



----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to