Fog Creek Software
Discussion Board

Welcome! and rules

Joel on Software

Source control for Windows development

Like many of you, I currently use Visual SourceSafe, and to say that it is limiting is a gross understatement (and it's apparently a case where Microsoft does not eat their own dogfood, but instead use a custom source control product internally). What is a better option for advanced source control?

Jimmy Chonga
Saturday, March 8, 2003

What problems do you have with VSS exactly? We use it with SourceOffSite ( that allows much speedier access to the repository over WAN/VPN connections (it basically turns VSS into a client/server system).

Alternatively there's CVS of course - plenty of dicussion on that on the main board. Use Jalindi Igloo ( ) to provide VS.NET integration to a CVSNT ( ) back end. But not as fast remotely over VPN for us as SourceOffSite.

Also, SourceGear have just brought out their own fully .NET source control system called Vault that uses SQL Server/MSDE for storage. Haven't looked into it yet - as SoS/VSS suits our requirements at the mo'.


Duncan Smart
Saturday, March 8, 2003

There are also and (haven't used either one, just throwing options into the pot).

And, in fact, MS does eat their own dogfood - at least in some places. Some teams at MS use VSS, some use SLM (internal tool) some use a custom version of Perforce. There are probably some on CVS too, though I haven't met any.

Mike Gunderloy
Saturday, March 8, 2003

Microsoft actually uses a lot of different products internally, and I think you'll find that inertia is the responsible party as much as anything else.

We use CVSNT, without VS.NET integration (don't see any point, personally). Our CVS wrapper of choice is Tortoise, which is very very cool. :)

Brad (
Sunday, March 9, 2003

Subversion looks like it'll be the giant most likely to topple the VSS and CVS dynasties.  At least when it is fully complete.  Decide for yourself.

Brent R. Matzelle
Tuesday, March 11, 2003

*  Recent Topics

*  Fog Creek Home