Choosing the right version control for your project
Azure Repos | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | VS 2017 | VS 2015 | VS 2013
Whether your software project is large or small, using version control as soon as possible is a good idea. Azure Repos supports two types of version control: Git and Team Foundation Version Control (TFVC).
Which version control system should I use?
Git is the default version control provider for new projects. You should use Git for version control in your projects unless you have a specific need for centralized version control features in TFVC.
You can use TFVC repos with Git in the same Project so it's easy to add TFVC later if you need centralized version control. To setup a new repo type for an existing project use these instructions.
Git is a distributed version control system. Each developer has a copy of the source repository on their dev machine. Developers can commit each set of changes on their dev machine and perform version control operations such as history and compare without a network connection. Branches are lightweight. When you need to switch contexts, you can create a private local branch. You can quickly switch from one branch to another to pivot among different variations of your codebase. Later, you can merge, publish, or dispose of the branch.
Git in Visual Studio, Azure DevOps Services, and TFS is standard Git. You can use Visual Studio with third-party Git services, and you can also use third-party Git clients with TFS.
To learn more, see Git and Azure Repos.
Team 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 has two workflow models:
Server workspaces - Before making changes, team members publicly check out files. Most operations require developers to be connected to the server. This system facilitates locking workflows. Other systems that work this way include Visual Source Safe, Perforce, and CVS. With server workspaces, you can scale up to very large codebases with millions of files per branch and large binary files.
Local workspaces - Each team member takes a copy of the latest version of the codebase with them and works offline as needed. Developers check in their changes and resolve conflicts as necessary. Another system that works this way is Subversion.
To learn more, see TFVC overview
Moving from TFVC to Git
Git and TFVC capabilities
Need more help to make a choice? These charts might help.
Team members can concurrently change files on their dev machines. You upload (check-in) changesets to the server when you create them. You can upload your changes at any time. However, you might be interrupted by conflicts.
You can change the comment of a changeset after you check it in. You can link changesets to work items and associate them with completed builds.
Team members can concurrently change files on their dev machines. You create commits on your dev machine independently of contributing them to the team. When you're ready you must pull the latest commits before you upload (push) yours to the server. When you pull, you might be interrupted by conflicts.
You can amend the latest local commit. You cannot change older commits. You can link commits to work items and associate them with completed builds.
You can modify and combine local commits from the command prompt.
Path-based branches are used mostly as long-standing constructs to isolate risk of change among feature teams and releases. Team members typically set up an additional workspace for each branch they work on.
Changes in each branch are independent from each other, so you don't have to check them in before switching from one branch to another. Merging between sibling branches requires a baseless merge.
You can get visualizations of your branch structures and where your changesets have been merged.
Branching is lightweight and path independent. Many developers create a branch for each new feature they are coding, sometimes on a daily basis. You can quickly switch from one branch to another to pivot among different variations of your codebase. You can create branches that exist only on your dev machine and share them if and when you're ready.
You must commit, branch, stash, or undo changes before switching branches. Merging is simple and independent of the commit that the branch is based on.
You can compare branches to see which commits exist on which branches.
You might have to resolve conflicts when you get, check in, merge, or unshelve. You can resolve all types of conflicts in Visual Studio.
You might have to resolve conflicts when you pull or merge. You can resolve content conflicts in Visual Studio or from the command prompt.
You can check in large binary files. You might also want to use NuGet in combination or as an alternative.
You can check in small binary files as you would regular files. When working with large binary files, use Git-LFS to store your large binary files in Azure Repos.
File history is not replicated on the client dev machine and so can be viewed only when you're connected to the server. You can view history in Visual Studio and on the web portal. You can annotate files to see who changed a line, and when they changed it.
File history is replicated on the client dev machine and can be viewed even when not connected to the server. You can view history in Visual Studio and on the web portal. You can annotate files to see who changed a line, and when they changed it.
Tag your files
You can apply labels to a version of one or more files from either Visual Studio or the command prompt. Each file can have label applied to a different version.
You can apply tags from the command prompt to individual commits. View tags in the Visual Studio history window.
Roll back changes
You can roll back one or more changesets
You can revert a commit.
You can quickly begin small projects. You can scale up to very large projects, but you have to plan ahead to modularize your codebase. You can create multiple repositories in a project.
Azure DevOps Services, TFS
Azure DevOps Services, TFS and Git third-party services
Team members can receive email alerts when check-ins occur.
Team members can receive email alerts when commits are pushed to the server.
Because your team checks in all their work into a centralized system, you can identify which user checked in a changeset and use compare to see what they changed. Looking at a file, you can annotate it to identify who changed a block of code, and when they did it.
You can identify which user pushed a commit. (Anyone can claim any identity as the author or committer.) You can identify when changes were made and what was changed using history, compare, and annotate.
Builds (automated by TFBuild)
You can use all TFBuild capabilities to build any combination of content you want within the project collection.
You can use most TFBuild capabilities to build one project at a time, and one or more repositories at a time.
Yes; see Day in the life of an devops Developer: Suspend work, fix a bug, and conduct a code review. For more lightweight discussions, you can also comment on and send email about a changeset from the web portal.
Yes; see Conduct a pull request. For more lightweight discussions, you can also comment on and send email about a commit from the web portal.
You can browse your files on the web portal and using Source Control Explorer in Visual Studio.
Your project exists on only one server.
Each project can contain one or more Git repositories and each Git repository can contain one or more branches. The most granular permissions you can apply are to a repository or a branch. Files cannot be locked.
You can browse your files on the web portal.
You can push commits to multiple remote repositories (for example to both your project repository and to your web site hosted on Windows Azure.
You can use CI builds, gated check-in builds and check-in policies.
You can use CI builds and gated check-in builds through branch policies.
Visual Studio, Eclipse (with Team Explorer Everywhere)
Visual Studio, Eclipse, and other third-party tools
You can browse your files using Windows File Explorer or the command prompt.
Manage work on your dev machine
Changes, commits, and branches pages.
Suspend your work
You can create a branch from (from Visual Studio or the command prompt) or stash (from the command prompt)
- Visual Studio: Offers all commonly used features and many advanced features.
- TFS web portal: Can browse, comment, annotate, and see history of the codebase.
- TF Command prompt: Installed with Visual Studio. Used for advanced, administrative, and other less common tasks.
- Visual Studio: Offers many commonly used features. Features for some common tasks are not yet available.
- TFS web portal: Can browse, comment, annotate, and see history of the codebase.
- Third-party command prompt: You can install it from Visual Studio. Used for some common and many less common tasks.
Visual Studio compatibility
You can use all supported previous versions of Visual Studio.
Git is built in with Visual Studio 2017, 2015, and 2013.
You can also use Visual Studio 2012 Update 4 (you must also install Visual Studio Tools for Git).
You can browse your codebase (including branches), view history, annotate and comment on changesets and shelvesets, and perform other tasks such as ad hoc downloading of selected parts of your codebase as a .zip file.
You can browse your codebase, view history, compare branches, annotate and comment on commits, and perform other tasks such as ad hoc downloading of selected parts of your codebase as a .zip file.
Integration and migration