Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> > Another approach may be to have an often "CVS Updated" > > development server. > > Hows that sound? > > That sound a little more like the model I'm after. However, as ASP > doesn't compile, the way to test code before committing is to run it > through a web server. This brings me back to the sites * projects * > developers problem. Hi Drew, Here's another idea. Let's assume that you have a central web server. And let's assume that the web server files will NEVER be modified on the web server; that is, they're effectively read-only. These files are served by IIS, and also shared (just to you) with a share. Your sandbox(es) would be on your desk machine. When you want to test your changes, you could copy your files to your share on the development server. You can then point a browser at the dev server. Using copy is ok because you never want to pull source from the server back to your machine - it's one way. And because you're using copy, you don't have to commit things into CVS until your changes have been tested. Regards, Mitch. ---------------------------------------------------------------------------- ------------------------ The information contained in this message and any attachments is confidential and intended for the named recipient(s). If you have received this message in error, please contact sender by return e-mail and destroy the message and any attachments. Any opinions or undertakings expressed in this message are those of the individual sender except where the sender expressly and with authority states them to be the opinions of Extel. ---------------------------------------------------------------------------- ------------------------