Source Control (2), MS TFS - Centralized Server App

Introduction

On September 10, 2018 Microsoft renamed VSTS to Azure DevOps and by Q1 2019 will rename TFS to Azure DevOps Server, and upgrade both with the same new user interface.

Azure DevOps (VSTS) is a hosted cloud offering, and Azure DevOps Server (TFS), is an on-premises version. Both offer functionality that cover multiple stages of the DevOps lifecycle including planning tools, source code management (SCM), and CI/CD.

As part of their SCM functionality, both platforms offer two methods of version control.

Git (distributed) - each developer has a copy on their dev machine of the source repository including all branch and history information.
Team Foundation Version Control (TFVC), a centralized, client-server system - developers have only one version of each file on their dev machines. Historical data is maintained only on the server.

Microsoft recommends customers use Git for version control unless there is a specific need for centralized version control features. https://docs.microsoft.com/en-us/vsts/tfvc/comparison-git-tfvc

This is noteworthy given that in June of 2018 Microsoft purchased GitHub, the Internets largest online code repository. This deal closed on Oct 26th, 2018.

--- the paragraph above is from Azure DevOps (TFS/VSTS) vs. GitLab, as an introduction.

This is the structure of this article,

Introduction
TFS
Visual Studio - TFS
TFSC Environment Setup
- Connect to TFS Server
- Connect to Team Projects
- Setting Local Path
TFSC Overview
- Key Concepts
  - Changesets
    - Integrated Check-in
    - Check-in Policies
  - Workspaces
  - Shelving
- Other Concepts
  - Labeling
  - Compare/Diff --- Source Control (2-1), TFS --- Comparison
  - Branching & Merging --- Source Control (2-2), TFS --- Merge