My development strategy on Win2k is CFStudio with a single user version of
CFServer locally. Depending on the Win2k version either IIS or Personal Web
Server, locally. Then a QA Staging box (or boxes if you're rich) in the same
environment as production and as near to production as possible in
configuration. Test the hell out of the code on the development boxes and
live in the logs before releasing it to QA. I am looking at QUME Content
Versioning but haven't used it long enough to make a technically accurate
statement. It looks good so far.
Kind Regards - Mike Brunt
Sempra Energy
213.244.5226
-----Original Message-----
From: Denis Piquette [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 10, 2001 5:25 PM
To: CF-Talk
Subject: Developers Desktop.
Can anyone offer any comments on a standard developers desktop when
developing for a MS CF site?
In W2K, do you use IIS with CF server loaded locally or on a Network?
What type of Source Control do you use?
What tool is best when developing cfx_Tags?
How about using MTS??
.
.
.
.
Thanks,
Denis Piquette
I.S. Manager
140 Fullarton, Suite 700
London, Ontario
519-672-6703 x212
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
