All:
This question is not directly related to ASP, but more to the web site
development and maintenance process.
I am having trouble maintaining all the ASP pages that I've been creating.
I'm finding myself working directly on (and often experimenting) with my
production system, often screwing things up while someone is trying to
access my files. I'd prefer to work on a development system, then deploy to
the production system, using some sort of "versioning" or source control.
To help simplify maintenance, I'm adopting a modular approach. I try to
isolate individual "panels" of a web page into their own ASP files, and
depend heavily on $Response->Include to construct the main page.
I'm familiar with CVS, but am unsure how to best leverage this technology
into a httpd environment.
Is anyone aware of "best practices" and/or "strategies" for managing the
development and enhancement of ASP sites? I've heard of DAV, but prefer to
use FrontPage as my editor, so I'm unsure of how to integrate the two.
Any URLs, suggestions, thoughts, comments, or words of wisdom would be
greatly appreciated!
JL
------
John D. Leonard II, Associate Professor Phone: 404/894-2360
School of Civil and Environmental Engineering FAX: 404/894-2278
Georgia Institute of Technology http://traffic.ce.gatech.edu
Atlanta, GA 30332-0355 mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
