Visual Studio Team System

I was at the DC launch for Visual Studio 2005 and SQL Server 2005 yesterday, and was fortunate enough to sit through a few talks on Visual Studio Team System.  So naturally,  I now want to install the server (VSTS) – currently in Beta 3 – and hook Visual Studio 2005 to it.

There are multiple versions of Visual Studio 2005 available (Express, Standard, Professional, and Team System).  If you have a non-Team System version installed you will need to install the TS edition.  I am not sure on the accuracy of information I found on the Internet, but apparently, if you have the professional version installed you need not uninstall it before installing the TS version.  Both versions live side-by-side (yeah we’ve heard that before) and when you execute either version the higher SKU will execute no matter which icon you double click.  I wonder how much extra space is need for side-by-side.

I plan to install VS2005 TS at the office and then beg the IT guys at the office if they’ll donate a server for VSTS.

4 thoughts on “Visual Studio Team System

  1. http://

    VSTS is nice, but it isn’t the holy grail. Quite frankly, much of this functionality already exists for free in the .NET world. NUnit, NAnt, and NDoc even do some things better than VSTS. Play around with it.

  2. Rob Garrett

    Sure, I see your point, but one of the things I like about VSTS is the collaborative environment it offers. For example, the IT dept can provide an infrastructure document and VSTS allows architects to map applications on the system architecture diagram to the infrastructure.
    <br>
    <br>Seems dumb? Not really, on my current project the IT group and development group did not communicate well about what software applications would run on what servers.
    <br>
    <br>VSTS also keeps tabs on work items. I want to see if it does a better job than MS Project, which seems to rely on the PM doing a good job at keeping it up to date.

  3. G. Andrew Duthie

    Hey Rob,
    <br>
    <br> Just wanted to offer a slight correction. The Visual Studio Team System editions (Team Edition for Software Developers, Team Edition for Software Architects, and Team Edition for Software Testers) don’t install side-by-side with Visual Studio 2005 Professional…rather, they layer on additional features within the same IDE. It’s all Visual Studio, but what features are available depends on which edition you install.
    <br>
    <br>So if you have Visual Studio 2005 Professional installed, and then you install Visual Studio 2005 Team Edition for Software Developers, you will have all of the functionality of both when you open up the Visual Studio 2005 IDE.
    <br>
    <br>If you want the full kit, you should consider the Team Suite, which includes all of the Team System editions in one package.
    <br>
    <br>And, of course, for the work item tracking, reporting, build server, source control, etc., you will need to install the Team Foundation Server, which is a separate product.
    <br>
    <br>Hope that clarifies things somewhat. Feel free to drop me a line via my blog contact page if you have any other questions about how all the pieces fit together.

  4. Rob Garrett

    Great, thanks Andrew, this makes everything clear. I had suspicions that installing the TS version would only install the missing components, but I wasn’t sure.
    <br>
    <br>I am in the process of setting up VSTS on a separate machine, after this is complete I’ll install the TS version on my workstation.
    <br>
    <br>I’ll drop you a line if I run into problems.
    <br>
    <br>Thanks.

Comments are closed.