|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
Team Foundation Version Control
You can use Team Foundation version control to manage multiple revisions during development of source code, documents, work items, and other critical information that is being worked on by your team.
Team Foundation version control includes the following version control features:
Check-ins for a group of items or for single changes.
Branching and merging.
A graphical-user interface.
A command-line interface.
There are two primary types of roles that use Team Foundation version control.
Contributor A contributor typically uses version control for adding, deleting, and modifying files, maintaining a historical record of all changes. For more information, see Working with Version Control Files and Folders.
A contributor uses Team Foundation version control to:
Check out files to their local workspace.
Check in modified files.
Add new files to the version control server.
Delete files from the version control server.
Merge changes between files.
Administrator An administrator manages the version control server by maintaining the integrity of data stored on it. The administrator manages the workgroups, permissions, setup, and check-in policies. For more information, see Administering Team Foundation Version Control.
An administrator uses Team Foundation version control to:
Configure the version control environment settings.
Control access to the version control database.
Destroy version-controlled files or folders.