Book Image

Microsoft Team Foundation Server 2015 Cookbook

By : Tarun Arora
Book Image

Microsoft Team Foundation Server 2015 Cookbook

By: Tarun Arora

Overview of this book

Team Foundation Server (TFS) allows you to manage code repositories, build processes, test infrastructure, and deploy labs. TFS supports your team, enabling you to connect, collaborate, and deliver on time. Microsoft's approach to Application Lifecycle Management (ALM) provides a flexible and agile environment that adapts to the needs of your team, removes barriers between roles, and streamlines processes. The book introduces you to creating and setting up team projects for scrum teams. You'll explore various source control repositories, branching, and merging activities, along with a demonstration of how to embed quality into every code check-in. Then, you'll discover agile project planning and management tools. Later, emphasis is given to the testing and release management features of TFS which facilitate the automation of the release pipeline in order to create potentially shippable increments. By the end of the book, you'll have learned to extend and customize TFS plugins to incorporate them into other platforms and enable teams to manage the software lifecycle effectively.
Table of Contents (16 chapters)
Microsoft Team Foundation Server 2015 Cookbook
Credits
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Index

Continuous synchronization with the TFS Proxy server


It is not uncommon today to have geographically distributed Teams accessing TFS from remote locations. Remote users may suffer from latency of the connection between their location and the location where TFS is hosted. The Team Foundation Proxy Server comes to the rescue here. There is a common misconception about TFS Proxy caching all requests. However, the proxy server only caches the Get operation for TFVC-based version control. The proxy server does not carry out a continuous synchronization or replication operation, instead it caches the item on first request. While the first caller from the remote location will still face the latency in their get operation, all future requests will get the data as if it was being accessed locally. Today, developers are encouraged to check in code frequently. This means geographically distributed Teams operating in low network bandwidth regions will notice a lag when performing a get operation on...