Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. What is Team Foundation Version Control?
In this articleAzure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018 Visual Studio 2022 | Visual Studio 2019 | Visual Studio 2017 | Visual Studio 2015 | Visual Studio 2013 Whether your software project is large or small, using version control as soon as possible is a good idea. Version control systems are software that help you track changes you make in your code over time. As you edit your code, you tell the version control system to take a snapshot of your files. The version control system saves that snapshot permanently so you can recall it later if you need it. Azure DevOps Services and TFS provide two models of version control: Git, which is distributed version control, and Team Foundation Version Control (TFVC), which is centralized version control. This article provides an overview and a starting point for using Team Foundation Version Control. If you're deciding which type of Azure DevOps Services/TFS version control to use, see Choosing the right version control for your project. Why use version control?Without version control, you're tempted to keep multiple copies of code on your computer. This is dangerous, as it's easy to change or delete a file in the wrong copy of code, potentially losing work. Version control systems solve this problem by managing all versions of your code but presenting you with a single version at a time. Version control systems provide the following benefits:
There are plenty of things that can take up your time as a developer: reproducing bugs, learning new tools, and adding new features or content. As the demands of your users scale up, version control helps your team work together and ship on time. Team Foundation Version ControlTeam Foundation Version Control (TFVC) is a centralized version control system. Typically, team members have only one version of each file on their dev machines. Historical data is maintained only on the server. Branches are path-based and created on the server. TFVC lets you apply granular permissions and restrict access down to a file level. Because your team checks all its work into Team Foundation Server, you can easily audit changes and identify which user checked in a changeset. By using compare and annotate you can identify the exact changes that they made. QuickstartsGet started by creating a project, configuring your workspace, and reviewing and sharing your code. You can use any one of these clients or IDEs:
Step-by-step tutorialsLearn the basics of working in TFVC with the following tutorial which shows a day in the life of a devops developer using Visual Studio and TFVC.
What do you want to do?
Operations available only from the tf command lineThe following table lists tasks for Team Foundation version control that you can perform only at a command prompt using the tf command line tool.
Related articles
FeedbackSubmit and view feedback for What are the characteristics of a version control system?Features of a version control system. Reliable: keep versions around for as long as we need them; allow backups.. Multiple files: track versions of a project, not single files.. Meaningful versions: what were the changes, why where they made?. Revert: restore old versions, in whole or in part.. Compare versions.. Which one of the following is a centralized version control?Centralized source control systems, such as CVS, Perforce, and SVN, require users to pull the latest version from the server to download a local copy on their machine.
What is a centralized version control system example?The most well-known examples of centralized version control systems are Microsoft Team Foundation Server (TFS) and SVN.
Which of the following is a version control system?There are two types of version control: centralized and distributed.
|