New on MSDN: Installing the December CTP Release of Visual Studio Team System

Installing the December CTP Release of Visual Studio Team System
David C. Bost
Solution Partners, Inc.

February 2005

Summary: Use this step-by-step guide to install and configure the latest release of Team System in a virtual environment using Virtual PC 2004. (26 printed pages)

Requirements   Windows XP with Virtual PC 2004 or Windows Server 2003 with Virtual Server 2005


  • Introduction
  • Setting Up Virtual PC for the Team Foundation Tiers
  • Setting Up the Team Foundation Data Tier
  • Setting Up the Team Foundation Application Tier
  • Setting Up the Team Foundation Client Tier
  • Setting Up Visual Studio with Team Foundation Functionality
  • Additional Resources
Comments (6)

  1. Don says:

    You’re kidding, right?

    It takes 26 pages of instructions to explain how to install this release? And your previous release forced some of us to do a complete windows reinstall after the VSTS installation failed? Do you have any idea how bad these releases are making your team look?

    There is no software that I’m more excited about than VSTS, but PLEASE sit everyone down and get a grip on your install process before the next build goes out. If it still takes 26 pages to install, walk through those 26 pages yourself and ship the completed VirtualPC images so that installation becomes (1) Unzip this file (2) change the default password (3) run VSTS. THAT’s an install story.

    VSTS is the best conceived product I’ve ever seen but frankly speaking the install stories for your betas have made your team look nothing short of incompetent. PLEASE do the right thing. I still believe in VSTS but if the third release is as absurd as this one, I’m going to have to give up on the product.


  2. Rob Caron says:

    We could easily trim down the content and simply say, "Install Windows Server 2003, IIS, SQL Server 2005 and Windows SharePoint Services." That would eliminate most of the content. With this article, we were trying to provide a set of "one-stop shopping" directions for installing Team System in a virtual environment. Several people have found this very useful.

    Also, MSDN uses the Microsoft Word printed page count (26 pages), not the actual Web printed page count (19 pages, if you don’t count the feedback section on page 20). In contrast, the Installation Guide for Microsoft Project Server 2003 is a 259 page PDF file.

  3. Don Alvarez says:

    >We could easily trim down the content and simply say …

    I disagree. Having looked into the installation myself prior to David Bost’s writeup, and haaving seen the difficulties that others have had with the installation ( for example), and having experienced first hand the problems that I and others had with the previous release, it is clear that even someone who knows what they are doing is going to have a hard time getting this system installed.

    You say that the instructions could be compressed to "Install Windows Server 2003, IIS, SQL Server 2005 and Windows SharePoint Services." I have a box running Windows Server 2003 (as does Sam Gentile, I would assume). It’s already running IIS and SharePoint services (as is Sam’s, undoubtedly). I don’t recall whether I have SQL Server 2005 on it yet or not, but lets assume that I do. The problem isn’t installing those apps (a task needing only one word of details). The problem is configuring those apps. What I saw, what Sam Gentile experienced first hand, and what David Bost demonstrated when he wrote his article is that getting VSTS installed and running (by which I mean properly configured) is an extremely length and fragile process. That lengthy and fragile process is a very, very serious flaw in your product.

    My best guess is that the PM’s on VSTS have somehow mistakenly concluded that anyone who will be running VSTS will have a huge IT staff with time to burn figuring out how to get VSTS configured. NOT TRUE. I run a single developer shop, and I’m can’t wait to get my hands on VSTS. Sam Gentile (to the best of my knowledge) is essentially a single developer shop (albeit an extremely competent, well known, and well connected one). VSTS is the natural progression of VSS and NUnit. It has great team features but you don’t need a team to need it.

    Also, every MS bizdev person I’ve heard speak in the past year has talked about how the focus is on midsize businesses. Currently, the install story for VSTS looks to be beyond the capability of a great many (most?) midsize businesses (have you ever listened to a conversation in a small game studio about how to configure SourceSafe, for example? it’s not pretty).

    Please hear what I’m saying. I want VSTS to succeed. My criticisms of the VSTS install story are very serious but they are intended as constructive criticism. You can fix the install story. It will not be easy to fix, but it is far more efficient for your team to take the time to fix it once than for every user of VSTS to have to burn the time currently required to intsall the product.

    I say again, PLEASE fix your install story. It is an incredibly serious problem. It WILL kill your product if it is not corrected.


  4. Rob Caron says:

    Don’t get me wrong – I’m not saying that our current installation is painless. Quite the contrary. We asked Dave to write that article to fill a near-term need that would help people evaluate the actual product. Meanwhile, back at the ranch, we are working to improve the install story and it will get better. Any development team that wants to use it should be able to install and configure Team System. In another month or so you’ll see the first Beta release of Team System. When you see it, I hope you’ll agree we’re heading in the right direction.

  5. Don says:

    Great to hear. I’m only being hard on you because I want VSTS to completely rock when it releases.

    I can’t wait.


  6. Jason Shaver says:

    Is there a way to get these documents as word files? I hate printing web-pages?

Skip to main content