1427 Professional Team Foundation Server 2012
PROFESSIONAL TEAM FOUNDATION SERVER 2012 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
⊲ PART I GETTING STARTED
CHAPTER 1 Introducing Team Foundation Server 2012 . . . . . . . . . . . . . . . . . . . . . . . . . 3 CHAPTER 2 Planning a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 CHAPTER 3 Installation and Confi guration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 CHAPTER 4 Connecting to Team Foundation Server . . . . . . . . . . . . . . . . . . . . . . . . . . 59 ⊲ PART II VERSION CONTROL CHAPTER 5 Overview of Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 CHAPTER 6 Using Team Foundation Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . 95 CHAPTER 7 Ensuring Code Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147 CHAPTER 8 Migration from Legacy Version Control Systems . . . . . . . . . . . . . . . . . . .177 CHAPTER 9 Branching and Merging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 CHAPTER 10 Common Version Control Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 ⊲ PART III PROJECT MANAGEMENT CHAPTER 11 Introducing Work Item Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 CHAPTER 12 Customizing Process Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 CHAPTER 13 Managing Teams and Agile Planning Tools . . . . . . . . . . . . . . . . . . . . . . . 311 CHAPTER 14 Reporting and SharePoint Dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . 333 CHAPTER 15 Project Server Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 ⊲ PART IV TEAM FOUNDATION BUILD CHAPTER 16 Overview of Build Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 CHAPTER 17 Using Team Foundation Build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 CHAPTER 18 Customizing the Build Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
(Continued)
⊲ PART V ADMINISTRATION
CHAPTER 19 Introduction to Team Foundation Server Administration . . . . . . . . . . . 493 CHAPTER 20 Scalability and High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 CHAPTER 21 Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 CHAPTER 22 Security and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 CHAPTER 23 Monitoring Server Health and Performance . . . . . . . . . . . . . . . . . . . . . . 599 CHAPTER 24 Testing and Lab Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627 CHAPTER 25 Upgrading from Earlier Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657 CHAPTER 26 Working with Geographically Distributed Teams . . . . . . . . . . . . . . . . . . 675 CHAPTER 27 Extending Team Foundation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
PROFESSIONAL
Team Foundation Server 2012
Ed Blankenship
M artin Woodward
Grant H olliday
Brian Keller
Professional Team Foundation Server 2012 Published by John Wiley & Sons, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 Copyright © 2013 by John Wiley & Sons, Inc., Indianapolis, Indiana Published simultaneously in Canada
ISBN : 978-1-118-31409-8
ISBN : 978-1-118-43932-6 (ebk)
ISBN : 978-1-118-60452-6 (ebk)
ISBN : 978-1-118-60460 -1 (ebk) M anufactured in the United States of America 10 9 8 7 6 5 4 3 2 1
N o part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means,
electronic, mechanical, photocopying, recording, scanning or other wise, except as permitted under Sections 107 or 108
of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, M A 01923, (978) 750 -840 0, fax (978) 646 -860 0. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 R iver Street, H oboken, N J 07030, (201) 748-6011, fax (201) 748-60 08, or online atLimit of Liability/ Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifi cally disclaim all warranties, including
without limitation warranties of fi tness for a particular purpose. N o warranty may be created or ex tended by sales or pro-
motional materials. The advice and strategies contained herein may not be suitable for every situation. This work is sold
with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services.
If professional assistance is required, the services of a competent professional person should be sought. N either the pub-
lisher nor the author shall be liable for damages arising herefrom. The fact that an organization or Web site is referred to
in this work as a citation and /or a potential source of further information does not mean that the author or the publisher
endorses the information the organization or Web site may provide or recommendations it may make. Further, readersshould be aware that Internet Web sites listed in this work may have changed or disappeared bet ween when this work was
written and when it is read.For general information on our other products and services please contact our Customer Care Department within the United States at (877) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-40 02 . Wiley publishes in a variety of print and electronic formats and by print-on-demand. Some material included with
standard print versions of this book may not be included in e-books or in print-on-demand. If this book refers to media
such as a CD or DVD that is not included in the version you purchased, you may download this material atLibrary of Congress Control N umber: 2012950503
Trademarks: Wiley, the Wiley logo, Wrox, the Wrox logo, Programmer to Programmer, and related trade dress are trade-
marks or registered trademarks of John Wiley & Sons, Inc. and /or its affi liates, in the United States and other countries,
and may not be used without written permission. [Insert third-party trademark information] All other trademarks are the
property of their respective owners. John Wiley & Sons, Inc., is not associated with any product or vendor mentioned in
this book.
To M om , D ad, N athan, T iffany, Z ach, D aniel, M ik e,
and G randm a, and to all those on the product team s
that m ak e this an am azing product that positively im pacts so m any in the softw are engineering com m unity.—Ed Blankenship To Catherine.
—Martin Woodward To m y w ife, Em m a.
—Grant Holliday
EXECUTIVE EDITOR
Katie Crocker
VICE PRESIDENT AND EXECUTIVE GROUP PUBLISHER
Richard Swadley
VICE PRESIDENT AND EXECUTIVE PUBLISHER
Neil Edde
ASSOCIATE PUBLISHER
Jim Minatel
PROJECT COORDINATOR, COVER
PROOFREADER
PRODUCTION MANAGER
Jennifer Bennett
INDEXER
Robert Swanson
COVER DESIGNER
Ryan Sneed
COVER IMAGE
© Steve Pepple / iStockphoto
Tim Tate
Amy Knies
Robert Elliott
Mike LaBonne
PROJECT EDITOR
Christina Haviland
TECHNICAL EDITORS
Steve St. Jean Brian Keller
PRODUCTION EDITOR
Kathleen Wisor
COPY EDITOR
EDITORIAL MANAGER
BUSINESS MANAGER
Mary Beth Wakefi eld
FREELANCER EDITORIAL MANAGER
Rosemarie Graham
ASSOCIATE DIRECTOR OF MARKETING
David Mayhew
MARKETING MANAGER
Ashley Zurcher
CREDITS
ABOUT THE AUTHORS ED BLANKENSHIP
works at M icrosoft as the program manager for the Lab and Environment M anagement scenarios of the Visual Studio ALM and Team Foundation Server product family. H is expertise with Team Foundation Server and Visual Studio ALM began with the beginnings of the product family nearly seven years ago.
Before joining M icrosoft, Ed was awarded as a M icrosoft M ost Valuable Professional (M VP) for fi ve years. H e was voted in 2010 as the M icrosoft M VP of the Year for Visual
Studio ALM and T FS by his peers. Ed was also a T FS consultant and the ALM practice technical lead at Imaginet (formerly N otion Solutions). Prior to consulting, Ed was the Release Engineering M anager at Infragistics, where he led a multiyear Team Foundation Server and Visual Studio Team System implementation globally to improve the development process life cycle.
Ed has authored and served as technical editor for several Wrox books. H e has also authored numerous articles and spoken at various user groups, events, radio shows, and conferences, includ- ing TechEd N orth America. You can fi nd him sharing his experiences at his technical blog at d on Twitter with his handle @EdBlankenship.
MARTIN WOODWARD
is a senior program manager for M icrosoft Visual Studio Team Foundation Server specializing on the Eclipse and Cross-Platform Tooling. Before joining M icrosoft, M artin was awarded M VP of the Year for Visual Studio Application Lifecycle M anagement and he has spoken about Team Foundation Server at events internationally.
GRANT HOLLIDAY
is a senior premier fi eld engineer (PFE) for M icrosoft Services in Australia. As a PFE, he works with customers to perform proactive health checks and workshops on Team Foundation Server. Prior to this role, he spent three years in Redmond, Washington, as a Program M anager in the Visual Studio Team Foundation Server product group. H e was responsible for the internal T FS server deployments at M icrosoft, including the largest and busiest T FS server in the world used by Developer Division. Grant was also involved in the early stages of getting the Team Foundation
Service up and running on the Windows Azure platform. Grant shares his thoughts on his blog at d presentations at industry events.
BRIAN KELLER
is a Principal Technical Evangelist for M icrosoft specializing in Visual Studio and application lifecycle management. Brian has presented at conferences all over the world and has managed several early adopter programs for emerging M icrosoft tech- nologies. Brian is a regular personality on M SDN ’s Channel 9 website, and he is cohost of the popular show “ This Week on Channel 9.” Brian has coauthored multiple books on Visual Studio and application lifecycle management. Brian was also one of the technical editors on this book.
ABOUT THE CONTRIBUTOR STEVEN ST. JEAN
is a senior ALM consultant with Imaginet (formerly N otion Solutions), a full- service consultancy working at the cutting-edge of M icrosoft technologies. H e has 20 years of industry experience, the past seven focused on assisting clients with maturing their development processes including the use of the M icrosoft tools stack. H e is a M icrosoft M VP in Visual Studio ALM , a certifi ed professional in Team Foundation Server (T FS), and technical editor of a number of books pertaining to ALM and T FS. H e speaks on various ALM process and tooling topics at user groups and code camps. In his free time he enjoys spending time with his wife and daughters, travel- ling, and photography. You can fi nd his technical blog atd his
Twitter handle is @SteveStJean. Steven was also one of the technical editors on this book.
ACKNOWLEDGMENTS
I WANT TO THANK
everyone involved with putting this book together, including the author team, editors, reviewers, and everyone who was able to give us great feedback and help along the way! Thanks to M artin, Grant, Brian, and Steve for the great teamwork and contributions that have made this book awesome. I have really appreciated you guidance along the way as well as all of the new things that I learned from each of your expertise. I truly enjoyed working with y’all. The help from the each of the product teams to put together such a great product can’t be dis- counted either. A personal thanks to Brian H arry, Sam Guckenheimer, M att M itrik, M ario Rodriguez, Anu, M uthu, Aseem, N ipun, Satinder, Gregg Boer, Jim Lamb, Jason Prickett, Chad Boles, Phillip Kelley, Christophe Fiessinger, and Chris Patterson on the product teams at M icrosoft. I appreciate all of your contributions, advice, and primarily your in-depth insight into the product over the years that has helped develop a better understanding of all the moving wheels of Team Foundation Server. I also want to thank my former M icrosoft M VP colleagues who have been a great group to be a part of, as well as to work with now. A special thanks goes to M ike Fourie, Tiago Pascoal, Anthony Borton, Steve Godbold, M ickey Gousset, Steve St. Jean, Chris M enegay, Dave M cKinstry, Joel Semeniuk, Adam Cogan, and N eno Loje for all of your help.
Thank you to everyone who has helped me throughout my career over the years. Thanks for pushing me to get better in my craft, and for fueling my enthusiasm. Thanks also to my family and friends for their guidance along the way and their constant support. I couldn’t have done this without each of you.
—Ed Blankenship FIRST, I WOULD LIKE
to thank my coauthors, Ed, Grant, and Brian, for allowing me to help them in putting this book together. I would also like to thank Steve St. Jean for his help and his attention to detail. You will struggle to meet a group of folks who know the breadth of Team Foundation Server better than these guys do, and it is a pleasure to work with them all.
M y colleagues in the entire Team Foundation Server group (past and present) have obviously been essential in the making of this book, and I would like to especially acknowledge the help, advice, and assistance from the following people both inside and outside M icrosoft: Aaron H allberg, Philip Kelley, Chad Boles, Buck H odges, M atthew M itrik, James M anning, Jason Prickett, Ed H olloway, Doug N eumann, Ed Thomson, Peter Provost, Terje Sandstrom, and William Bartholomew. I also want to thank the ALM Rangers and ALM M VPs that make the Team Foundation Server community such a vibrant one to be in. Finally, I would like to thank my wife, Catherine. I owe Catherine so much for so many things, both big and small. I know that she signed up for “ in sickness and in health” on that wonderful day in N ewcastle when she agreed to be my wife, but I’m pretty sure she’d have thought again if our vows had been “ in sickness and in health, through the course of four books, and the countless nights apart or vacation days messed up due to my husband not understanding the term work /life bal- ance.” H owever, luckily for me she’s a woman who keeps her promises. And I aim to spend the rest of my days trying to make her understand how grateful I am. For everything.
—Martin Woodward I’D LIKE TO THANK
everyone who made this book possible. O nce again, we formed the dream team of Team Foundation Server knowledge and experience. Thank you to my coauthors, Ed, M artin, Steve, and Brian. Thank you to the Wiley project team for keeping us on track and helping with the polish and production effort that a technical book like this deserves.
Secondly, I’d like to thank the M icrosoft Services team in Australia and the worldwide Premier Field Engineering team. As I returned home after some time in Corp, you have welcomed me with open arms into your organizations—I am truly honored to call myself a PFE. A big thank you to Brian H arry and the Team Foundation Server team in Redmond and Raleigh. The T FS team are truly world-class in their customer focus and I am lucky to work with such great technical talent.
Fina lly, I’d like to t ha n k my fa m ily for a ll t he late n ights a nd weekends it took to get t h is over t he line.
—Grant Holliday
CONTENTS
INTRODUCTION xxvii
PART I: GETTING STARTED CHAPTER 1: INTRODUCING TEAM FOUNDATION SERVER 2012
CONTENTS
xii
CONTENTS
CHAPTER 4: CONNECTING TO TEAM FOUNDATION SERVER
xiii
CONTENTS
Learning what’s New in Team Foundation Server 2012 Version Control
98
Diff erences Between the Eclipse and Visual Studio Clients 137
Confi guring Version Control 140
xiv
CONTENTS
xv
CONTENTS
xvi
CONTENTS
xvii
CONTENTS
xviii
CONTENTS
xix
CONTENTS
CHAPTER 17: USING TEAM FOUNDATION BUILD 389 Introduction to Team Foundation Build 389 Team Foundation Build Architecture 390 Setting up the Team Foundation Build Service 392 Installing Team Foundation Build 393 Confi guring the Team Foundation Build Service 393 Additional Software Required on the Build Agent 399 Working with Builds
xx
CONTENTS
Workfl ow Activities 449
xxi
CONTENTS
Defi ning Responsibilities 550
xxii
CONTENTS
xxiii
CONTENTS
xxiv
CONTENTS
CHAPTER 25: UPGRADING FROM EARLIER VERSIONS 657 Overview 658 In-Place Upgrades Versus Migrating to New Hardware
xxv
CONTENTS
INDEX 725 xxvi
INTRODUCTION
OVER THE PAST DECADE, M icrosoft has been creating development tools that have been designed for
the ever-growing engineering teams of software developers, testers, architects, project managers, designers, and database administrators. In the Visual Studio 2012 line of products, there are tools for each team member to use to contribute to a software release. H owever, it’s not enough to allow for awesome individual contributions. You must also organize the collaboration of those contributions across the larger team, including the stakeholders for whom the software is being built. Beginning in the Visual Studio 2005 release, M icrosoft introduced a new server product named Team Foundation Server to complement its development products. N ow in its fourth release, Team Foundation Server 2012 has grown with all of the investment from the past decade and fi ts nicely in the Visual Studio application lifecycle m anagem ent (A L M ) family of products. Before the Visual Studio 2010 release, the Visual Studio ALM family of products was given the brand of Visual Studio Team System, which is no longer used in the latest releases.
As you will fi nd out, Team Foundation Server is a very large product with lots of features for man- aging the software development lifecycle of software projects and releases. The authors of this book collectively gathered from their past experience since the fi rst release of Team Foundation Server to document some of the tips and tricks that they have learned along the way. The backgrounds of the authors are quite diverse—managing one of the largest Team Foundation Server environments, designing the collaboration pieces for non-.N ET development teams, evangelizing the Visual Studio and Team Foundation Server products, managing releases at a software development company, and a consulting background where customers are helped each week to solve real-world challenges by taking advantage of Team Foundation Server.
WHO THIS BOOK IS FOR
If you have been looking to Team Foundation Server to meet some of your software development team’s challenges for collaboration, then this book is for you. You may have seen the Team Foundation Server product in your M SDN subscription and decided to set up a new environment internally. You may now be wondering how to administer and confi gure the product. You may have also noticed the new, hosted Team Foundation Service offering by M icrosoft and wondered where to get started. This book is for everyone ranging from the developer using Team Foundation Server for day-to-day development, to the administrator who is ensuring that the environment is tuned to run well and build extensions to the product to meet the needs of their software development team. You may also be preparing for any of the new Application Lifecycle M anagement (ALM ) M icrosoft certifi cation exams for administering or using Team Foundation Server, and you will fi nd many of the exam top- ics covered in this book.
This book does not require any knowledge of Team Foundation Server to be useful, but it is not meant for developers or testers who are just starting out their craft. Team Foundation Server can be
INTRODUCTION
used for teams as small as one to fi ve team members to teams consisting of tens of thousands. Code samples in the book are presented in C#, but they could also be implemented in other .N ET lan- guages (such as Visual Basic.N ET). You can fi nd a road map for the book based on your team role later in this “ Introduction” under the section named “ H ow This Book Is Structured.”
WHAT THIS BOOK COVERS
This book covers a complete overview of the Team Foundation Server 2010 product and provides hands-on examples for using the product throughout many of the chapters. This book only covers the latest version of Team Foundation Server 2010 (including Service Pack 1 in some areas) and does not expose the reader to how to use earlier versions of Team Foundation Server.
The book is divided into fi ve main parts, with detailed chapters that will dive into each of the fea- ture areas of Team Foundation Server 2010.
‰
Part I—Getting Started ‰ Part
II—Version Control
‰ Part
III—Project M anagement
‰ Part
IV —Team Foundation Build
‰
Part V —Administration HOW THIS BOOK IS STRUCTURED You may have picked up this book and are wondering where to get started. This book has been
written so that you start reading in a particular chapter without needing to understand concepts introduced in previous chapters. Feel free to read the book from cover to cover, or, if you are in a hurry or need to reference a specifi c topic, jump to that particular chapter. The next sections describe where you might get started in the book based on your role and the topics that might be most relevant for you.
Developers There are plenty of features that are available for developers who are using Team Foundation Server.
You might begin by reading Chapter 4, “ Connecting to Team Foundation Server,” to get started with exploring the different options available for connecting to your server. After that, you can begin your review of the version control features available in Part II of the book:
‰ Chapter
5—“ O verview of Version Control”
‰
Chapter 6—“ Using Team Foundation Version Control”
‰ Chapter
7—“ Ensuring Code Q uality”
xxviii
xxix
‰
‰ Chapter
10—“ Common Version Control Scenarios” Finally, if you are interested in the testing and environment /lab management features available in Team Foundation Server, you can consult Part V of the book:
Chapter 9—“ Branching and M erging” ‰ Chapter
‰
6—“ Using Team Foundation Version Control”
Chapter 5—“ O verview of Version Control” ‰ Chapter
‰
capabilities, then you will want to familiarize yourself with the version control features (which is where you will store the source code for your automated tests) in Part II of the book:
Chapter 14—“ Reporting and SharePoint Dashboards” If you are a technical tester, and will be automating test cases using the numerous automated test
‰
13—“ M anaging Teams and Agile Planning Tools”
Chapter 11—“ Introducing Work Item Tracking” ‰ Chapter
Team Foundation Server and Visual Studio include a host of new features for testing. You might begin by reading Chapter 4, “ Connecting to Team Foundation Server,” to get started with exploring the different options available for connecting to your server. After that, you will want to increase your understanding of the work item tracking features (which help track test cases, bugs, tasks, requirements, and so on), as well as the project reporting features in Part III of the book:
INTRODUCTION ‰
Testers
18—“ Customizing the Build Process”
Chapter 17—“ Using Team Foundation Build” ‰ Chapter
‰
16—“ O verview of Build Automation”
‰ Chapter
14—“ Reporting and SharePoint Dashboards” Finally, if you want to automate your build process, you can take advantage of reviewing those fea- tures in Part IV of the book:
Chapter 13—“ M anaging Teams and Agile Planning Tools” ‰ Chapter
‰
11—“ Introducing Work Item Tracking”
‰ Chapter
10—“ Common Version Control Scenarios” O nce you have a good grasp of the version control features, you may want to familiarize yourself with the work item tracking and reporting features in Part III of the book:
Chapter 9—“ Branching and M erging” ‰ Chapter
24—“ Testing and Lab M anagement”
INTRODUCTION MICROSOFT TEST MANAGER
If you are using M icrosoft Test M anager (available if you have acquired either Visual Studio 2012 Ultimate, Visual Studio 2012 Premium, or Visual Studio 2012 Test Professional), you may want to consult the companion to this book,
Professional Application Lifecycle Management with Visual Studio
2012 (Indianapolis: Wiley, 2012). Several chapters in that book discuss the features
available in M icrosoft Test M anager for test case management, executing manual tests, starting exploratory test runs to generate test cases, fi ling rich actionable bugs, creating temporary environments for development and testing use, and auto- mating user interface tests. For more information about this book, visit
Project Managers and Business Analysts
As a project manager or business analyst, you will want to ensure that you have insight into the soft- ware release or project, and be able to interact. You may also be interested in what customizations are possible with the process that Team Foundation Server uses for your teams. Project managers might also be interested in the capability to synchronize project data in Team Foundation Server with a M icrosoft O ffi ce Project Server instance. Business analysts may want to create and track requirements, including the traceability options from inception to implementation. Additionally, project managers and business analysts may want to learn how to seek feedback from customers and stakeholders and turn that feedback into new requirements, change requests, or product backlog items. You might begin by reading Chapter 4, “ Connecting to Team Foundation Server,” to get started with exploring the different options available for connecting to your server. All of the features that would be relevant for project managers and business analysts are discussed in Part III of the book:
‰ Chapter
11—“ Introducing Work Item Tracking”
‰
Chapter 12—“ Customizing Process Templates” ‰ Chapter
13—“ M anaging Teams and Agile Planning Tools”
‰
Chapter 14—“ Reporting and SharePoint Dashboards” ‰ Chapter
15—“ Project Server Integration” Project managers and business analysts may also be introduced in the companion to this book,
(Indianapolis,
Professional Application Lifecycle Management with Visual Studio 2012 Wiley: 2012), which can be found at r further reading. xxx
INTRODUCTION Executive Stakeholders
Executive stakeholders fi nd plenty of use for Team Foundation Server by gathering insight into how software releases and projects are progressing, and often want easily accessible dashboards with the information. The executive that leads the engineering organization may also be interested in planning a Team Foundation Server deployment, including who should administer the server. Additionally with Team Foundation Server 2012 , development teams can request feedback from stakeholders who then can provide rich feedback using the new Feedback Client.
You might begin with the chapters in Part I of the book:
‰ Chapter
2—“ Planning a Deployment”
‰ Chapter
4—“ Connecting to Team Foundation Server” After you have a good understanding of the concepts in those chapters, you can then explore the necessary work item tracking and reporting features available in Part III of the book:
‰ Chapter
11—“ Introducing Work Item Tracking”
‰ Chapter
13—“ M anaging Teams and Agile Planning Tools”
‰ Chapter
14—“ Reporting and SharePoint Dashboards”
Team Foundation Server Administrators
If you fi nd yourself in the position of administering a Team Foundation Server instance, this book provides plenty of great information for performing that role. In Part I of the book, you might begin by reading Chapter 2 , “ Planning a Deployment,” to understand what is required for setting up a Team Foundation Server environment. You can then install a new server by going through
Chapter 3, “ Installation and Confi guration.” If you are upgrading from a previous version of Team Foundation Server, you may want to begin by reading through Chapter 25, “ Upgrading from Earlier Versions,” before you get started with the upgrade process. It is recommended that, as a Team Foundation Server administrator, you understand all of the aspects that end users will take advantage of, including version control, work item tracking, and automated builds. You can read all of the chapters in Parts I through IV for information about those aspects of Team Foundation Server. Additionally, Part V is dedicated to administrative topics that will be of interest to administrators:
‰ Chapter
19—“ Introduction to Team Foundation Server Administration”
‰ Chapter
20—“ Scalability and H igh Availability”
‰ Chapter
21—“ Disaster Recovery”
‰ Chapter
22—“ Security and Privileges”
xxxi
INTRODUCTION ‰
Chapter 23—“ M onitoring Server H ealth and Performance” ‰ Chapter
24—“ Testing and Lab M anagement”
‰
Chapter 25—“ Upgrading from Earlier Versions” ‰ Chapter
26—“ Working with Geographically Distributed Teams”
‰
Chapter 27—“ Extending Team Foundation Server” Extensibility Partner If you are interested in extending the capabilities of Team Foundation Server 2012 , you will fi nd
many opportunities and extensibility points throughout this book. You may want to begin by read- ing through Chapter 27, “ Extending Team Foundation Server.” You will also fi nd extensibility options covered in several other chapters of the book:
‰ Chapter
7—“ Ensuring Code Q uality”
‰
Chapter 12—“ Customizing Process Templates” ‰ Chapter
14—“ Reporting and SharePoint Dashboards”
‰
Chapter 18—“ Customizing the Build Process” WHAT YOU NEED TO USE THIS BOOK To perform many of the hands-on examples in the book, it will be helpful to have a Team Foundation Server 2012 environment or Team Foundation Service account that you can use to test
out the different features in the product. You do not necessarily need separate hardware, since you can now install Team Foundation Server 2012 on client operating systems such as Windows 8 and Windows 7. Don’t worry about setting up and confi guring a new Team Foundation Server 2012 environment yet, since you will learn about that in Chapters 2 and 3.
Chapter 1 discusses a few options on how to acquire Team Foundation Server, including an entire virtual machine image for demonstration purposes. Chapter 4 also discusses the different tools that you can use to connect to your Team Foundation Server environment that will be needed through- out the book.
The source code for the samples is available for download from the Wrox website at:
FURTHER LEARNING
Each of the authors periodically write technical articles about Team Foundation Server and other Visual Studio products from time to time that you may benefi t from for further learning. Feel free to check out the author’s blog sites and subscribe to them in your favorite RSS reader.
xxxii
INTRODUCTION ‰
Ed Blank enship—
‰ M artin
W oodw ard—
‰ G rant H olliday
‰ Brian
Keller— Additionally, the two main blogs and RSS feeds we would recommend to you following for all of the latest news and updates are listed below as well.
‰ Brian H arry
‰ V isual
Studio A L M Product T eam —
CONTINUOUS PRODUCT UPDATES AND RELEASE SCHEDULE
T he one main thing to learn from M icrosoft going for ward for the Visual Studio and Team Foundation Ser ver products is that the product teams will be shipping updates more frequently — roughly ever y three months. T hese updates will include a roll-up of performance and bug fi xes as well as new features that are completed. For those that will be using the hosted Team Foundation Ser vice, new updates and features are automatically deployed ever y three weeks.
The main thing to remember is that you will want to make sure you are always up to date on both your development machine where Visual Studio products are installed and also your Team Foundation Server environment servers. This book was written for the released version and includes some content and features included in the fi rst quarterly update.
You can fi nd out more information about this new release cadence for Visual Studio and Team Foundation Server at
CONVENTIONS
To help you get the most from the text and keep track of what's happening, we've used a number of conventions throughout the book.
WARNING W arnings hold im portant, not-to -be-forgotten inform ation that is
directly relevant to the surrounding tex t.NOTE N otes indicate notes, tips, hints, trick s, or asides to the current discussion. xxxiii
INTRODUCTION SIDEBAR Asides to the current discussion are offset like this.
As for styles in the text:
‰ We highlight new terms and important words when we introduce them. ‰ We show keyboard strokes like this: Ctrl+A. ‰ We show fi le names, URLs, and code within the text like so: persistence.properties . ‰
We present code in two different ways: We use a monofont type with no highlighting for most code examples.
We use bold to emphasize code that is particularly important in the present
context or to show changes from a previous code snippet.SOURCE CODE
As you work through the examples in this book, you may choose either to type in all the code man- ually or to use the source code fi les that accompany the book. All the source code used in this book is available for download at Specifi cally for this book, the code download is on the Download Code tab at:
You can also search for the book at ISBN (the ISBN for this book is 978-1-118-31409-8 to fi nd the code). And a complete list of code downloads for all current Wrox books is available at
M ost of the code on compressed in a .Z IP, .R AR archive, or similar archive format appropriate to the platform. O nce you download the code, just decompress it with an appropriate compression tool.
NOTE Because m any book s have sim ilar titles, you m ay fi nd it easiest to search
by ISBN ; this book ’s ISBN is 978 -1-118 -314 09-8.O nce you download the code, just decompress it with your favorite compression tool. Alternately, you can go to the main Wrox code download page at
aspx to see the code available for this book and all other Wrox books. xxxiv
INTRODUCTION ERRATA
We make every effort to ensure that there are no errors in the text or in the code. H owever, no one is perfect, and mistakes do occur. If you fi nd an error in one of our books, like a spelling mistake or faulty piece of code, we would be very grateful for your feedback. By sending in errata, you may save another reader hours of frustration, and at the same time, you will be helping us provide even higher quality information. To fi nd the errata page for this book, go to
And click the Errata link. O n this page, you can view all errata that has been submitted for this book and posted by Wrox editors. If you don’t spot “ your” error on the Book Errata page, go to