Three’s a Charm
It looks like the third iteration of Team Foundation Server might be a good one. I just finished reading Brian Harry’s post on TFS 2010 and it contains some interesting references.
SourceSafe Replacement?
I never could understand why TFS was often compared to SourceSafe. All the sessions on migrating from VSS to TFS, TFS for VSS users, etc. Is a team really going to migrate from VSS to TFS? Really? You have got to be kidding me! TFS is change management (to borrow a phrase from Rational), and VSS was barely version control.
… but now I think I get it …
All those VSS (or CVS, etc.) users were left stranded – there was no lightweight version control server for individuals (or very small teams). So they all went to SVN. Quick setup, version control, painful (but possible) branching and merging, command line, nice shell client, poor VS client, and all of that.
VSTS 2010
In steps Visual Studio Team System, Team Foundation Server, 2010.
- Can run locally on Windows 7 and Windows Vista client OS’
- Simple installation / Configuration
- Can optional use SQL Server express edition
- Can be installed on a domain controller
- Stand-alone version includes Work Item Tracking, Version Control
Note that this stand alone version also appears to include the build server/services!
I assume with the new project collections feature, you could move your SQL Express database over to a real SQL Server when your team gets a bit bigger. And good pricing is also on the Redmond minds.
Looks to me like they did their research. And did it well.
Nice.