I like installing the latest and greatest software. One thing missing from the Visual Studio 2005 puzzle was Team Foundation Server Beta 3 Refresh (TFS).
At home I have two computers available that both run Windows XP Professional. Both have 1 GB RAM. TFS only runs on Windows Server 2003 SP1. Because I want TFS to be portable for demo purposes I decided to install it in a virtual machine on my laptop.
So I dug up a pre-existing clean Windows Server 2003 Virtual PC image, copied it over to my laptop, and installed the following things on it:
Windows Server 2003 SP1
- All post-SP1 security updates
- SQL Server 2005 Developer Edition (*)
- SharePoint Services 2.0 with SP2
- VS 2005 Team Foundation Server Beta 3 Refresh
- VS 2005 Team Foundation Client Beta 3 Refresh
At home I don’t run an Active Directory, so I decided to try out TFS in Workgroup mode. I got two warnings from the SQL Server 2005 and the TFS prerequisite checkers, but those were to be expected. I could only allocate 700 MB for the VPC and that it is a tad too little for those two products. Everything installed without problems. The only thing I noticed is that TFS Setup suffers from the Microsoft Progress Bar Syndrome: the progress bar progresses steadily but hangs for minutes at the 99% mark.
Installing Team Foundation Client on the server gives you the Team Explorer in an otherwise empty Visual Studio 2005 Standard Edition IDE:
Since I had already installed Visual Studio 2005 Team Suite with the Team Foundation Client, the next step was connecting to TFS. This worked without any login boxes, because I had configured local accounts with the same username and password on both the client and the server. This account is a local administrator on the server, and as such is automatically a member of the Team Foundation Administrators.
After connecting I created a new Team Project. This is the result:
Thank you Microsoft for a job well done. Installing TFS is a breeze.
(*) Don’t forget to configure remote connections it if you choose this edition.