This evening I completed my first split-server (or dual server as it’s called in the guide) installation of Team Foundation Server 2008. I’ve installed TFS a few times now in single-server mode which is pretty crazy easy when you consider what you get (way more than SVN or CVS by themselves). Throughout the entire process I actually found myself RTFM step -by-step. For all the grief that Microsoft receives, you have to give them a ton of credit for their manuals, guides, and walk-throughs.
-
-
About
- As a software consultant and father of two I am innately challenged each day to improve my craft. This blog is one way I engage myself with those looking to teach and learn.
Ryan-
I didn’t know TFS had a dual server ability, cool. Thanks for posting.
Also, you have to be fair to SVN and CVS. You’re comparing apples to oranges. SVN and CVS weren’t designed to be a full SDLC tool.
I agree TFS rocks and it’s version control is getting better and better. When you compare TFS’s vc to SVN, SVN still wins.
There are definitely a lot of things about SVN (and CVS) that I prefer. Small footprint and the ability to readily install a new server are just two. On the client end, not so much. I like my Source Control integrated into Visual Studio and I’ve not found a compelling replacement for AnkhSVN that I like nearly as much as TFS/VSS integrated Source Control.
Also, while TFS is 10000% better than VSS over the network, SVN still wins.
I will say though, at this point, there is no comparable story on the SVN front for TFS. Yes there are tools you can piece-meal together for tracking Issues with checkins, but it’s rather loose and cumbersome. I think there are slightly different, though merging, audiences for SVN and TFS at this point.
A MiniTFS would be my personal request from the Team. A version build on SQL Express or Compact Edition that I can do a no-touch deployment of on my machine and just run. No IIS needed, just self hosted WCF services.