20 May 2004

More Source Control goodness

So I've gotten my hands on an evaluation copy of Borland Together for Visual Studio.NET, as well. Design tool rather than source control ....


Subversion + TortoiseSVN
Subversion + AnkhSVN
(Both plus Subversion command line client)
SourceGear Vault
Borland StarTeam

Vault and StarTeam both support the MS SCC API, so they'll integrate tightly into VS.NET... Anhk appears to but doesn't explicitly say one way or the other, and Tortoise is a Windows shell extension that uses WebDAV to talk to SVN.

My inclination is to favor by default a SCC compliant interface, since that's kind of required to play nicely with VFP without just treating all of its files as binary weirdness.

18 May 2004

Source Control Systems

So, here’re my requirements for a source control system:


1)       supported inside visual studio 2003 (SCC API compliant)

2)       Support (even if its bad) for versioning binary files

3)       Stable data store (Source Safe loses major points here)

4)       Low administrative overhead with teams of 40 or less.

5)       Support for multiple repositories with the same or sharply limited increase in administrative footprint

6)       Normal SCCS “retrospective” functionality – get old versions, compare versions, etc.

7)       Failsafe “Get current version” functionality / shadow directory that shows the most recent revision


Currently, I’m looking at two possible solutions: SourceGear Vault and Tigris’ Subversion. Looks like I will be doing some evaluation at home this week….


Compellingly enough, Vault is available for single users for free.

17 May 2004

Development Blogging

finding that reading the MSDN blogs is useful, if dense, I think I agree with Bandit0013 about the utility of a blog to keep the rest of the developers apprised of what's changing.

It's certainly better than trying to keep track of what people are muttering.

< mutter > I hate muttering. < /mutter >