Source Control for Web Projects

[Jeff Dillon]

What are people using for source control for ASP and HTML files? We have a
typical scenario here, a handful of developers working locally on
development, an internal staging server, then an external-facing production
web server, all Windows 2003. I'm quite familiar with Visual Sourcesafe, but
it doesn't easily allow (to my knowledge, anyway) to move ad-hoc files
through to production to fix high severity bugs on the fly. It requires
project labeling or "pinning" other files that have been checked-in but
aren't ready for prime time.

Other solutions?

thx

Jeff

 

[Jeff Cochran]

What are people using for source control for ASP and HTML files? We have a
typical scenario here, a handful of developers working locally on
development, an internal staging server, then an external-facing production
web server, all Windows 2003. I'm quite familiar with Visual Sourcesafe, but
it doesn't easily allow (to my knowledge, anyway) to move ad-hoc files
through to production to fix high severity bugs on the fly. It requires
project labeling or "pinning" other files that have been checked-in but
aren't ready for prime time.

Other solutions?

You want a source control product that can be bypassed...?

Jeff

 

[Jeff Dillon]

I want a source control system that can handle the scenario described, as I
stated.

I used one recently but the name escapes me..where each developer has their
own virtual directory on the master server (and/or locally) and they work in
their "sandbox"...the source control system manages ad-hoc updates as well
as the full release cycle.

Something like that

Jeff

 

[Jeff Dillon]

Just found this...

http://weblogs.asp.net/korbyp/archive/2004/05/24/140550.aspx