Professional Team Foundation Server

Introduction

At the time of writing this, Visual Studio Team System has been out for several months. In my previous book, Professional Visual Studio 2005 Team System (also published by WROX—ISBN: 0-7645-8436-7), the focus was specifically on the features of the product. This book takes a slightly different approach—rather than look at features, we will look at common tasks and scenarios around the entire software development lifecycle (SDLC).

NOTE

Team Foundation Server has an interesting history of codenames. The original codename for Visual Studio 2005 Team System is Burton (named after a ski equipment company). The majority of the features in Team Foundation Server include codenames derived from landmarks in North Carolina. (Microsoft has a development office based in Raleigh, NC.) For example, the Team Foundation Server SDK is codenamed Bodie (after the Bodie Island Lighthouse near Nags Head). Currituck is the codename for the Team Foundation Work Item Tracking feature (named after the Currituck Beach Lighthouse). The Cape Hatteras Lighthouse provided the namesake for Team Foundation Version Control. Finally, the Ocracoke Island Light provided the codename for Web and load testing. Rob Caron has provided a series of blog posts describing these landmarks in detail. You can read them at the following address: http://blogs.msdn.com/robcaron. The "Foundation" part of Team Foundation Server describes the foundation of support for team software development. The elements include ...