Version Control Integrations

Top |Previous |Next

Microsoft Team Foundation Server Integration

This section describes Collaborator integration with Team Foundation Server and its successor Azure DevOps Server.

GUI Client

The GUI Client can upload local changes to files in a Team Foundation Server Workspace. The GUI Client can also upload the files in a Shelveset or Changeset.

Command-Line Client

The Command-Line Client can upload local changes to files controlled by Team Foundation Server before they are checked in. The Command-Line Client can also upload the files in a Shelveset or Changeset.

Supported Versions

Team Foundation Server and Azure DevOps Server versions 2010 through 2020 are supported by the Command-Line Client and the GUI Client.

Our client integrations use Team Foundation Server SDK  to communicate with Team Foundation Server. Because of this, we support all protocols, authentications, proxies, and other client configuration options that are supported by SDK.

Remarks

Additionally to version control integration with Team Foundation Server, you can enable integration with TFS work items. This will allow synchronizing reviews and work items addressed in that reviews, appending the issues to the review's Remote System Links section and retrieving the item's current status. See Issue-Tracking Integrations: Overview for more information.

The Team Foundation Server integration will not work with non-English installations of Visual Studio .NET. Regional settings for other locales are supported, but installing a non-English Visual Studio prevents correct parsing of the TF command line output.

When using Team Explorer Everywhere clients our client will need access to the server for changelist information without being prompted for a password. To do this you will need to save your login information to your credentials cache using the TF_AUTO_SAVE_CREDENTIALS environment variable, which is documented here. Once you have set this you will need to use a mutating command (such as checkout, checkin, and so on) and enter your credentials one more time for it to stick.

Technical Details and Limitations

Review Screen, Diff Viewer, Eclipse Plug-in and Visual Studio Extension display atomic changelists (changesets in terms of TFS) in chronological order (from older to newer), regardless the order in which they have been uploaded to review.

Collaborator does not guarantee that Diff Viewer will display correct comparison results for the following cases:

If you have "gaps" while adding subsequent atomic changelists (changesets in terms of TFS) to the same review. For example, add changelists 1, 2, and 4, but forget to add changelist 3.
If you add pending changelists from different workspaces to the same review.
If you add several diffs (non atomic changelists) to the same review.

© 2003-2025 SmartBear Software. All rights reserved.