Azure DevOps Blog

DevOps, Git, and Agile updates from the team building Azure DevOps

Preparing to Migrate from Visual SourceSafe to Team Foundation Source Control

The Team Foundation Visual SourceSafe converter tool transfers files, folders, version history, and user information from a Visual SourceSafe database to a Team Foundation source control server. Before you move your files and historical information to Team Foundation, you should analyze and make a backup copy of the database, check in as many ...

Team Foundation Server Proxy and Source Control

The Team Foundation source control proxy is designed to boost network performance by caching copies of source control files in a remote location, local to the developer needing the files but away from the main source control location. By storing copies in the remote location, typically connected to the source location through a slower link ...

Remote Connections and Geograpically Dispersed Development

In response to a post from Tony dated 12/16/05 (sorry for the delay, I was on a skiing vaca) asking: "do you have anything on team foundation server source control for geographically dispersed development?"... Team Foundation Server provides support for distributed teams to use source control through the Team Foundation Server proxy. The proxy...

Configure Team Foundation Source Control to use Proxy Server

Team Foundation source control can be configured to provide enhanced performance for distributed teams by using proxy servers. The proxy server caches copies of source control files in the location of the distributed team, therefore significantly reducing the bandwidth-intensive operation of downloading files into a user’s workspace.Note...

About the Team Foundation Server Proxy Config File

The Team Foundation Server Proxy has a separate XML configuration file that maintains information required for the proxy configuration. This topic describes the nodes found in this file and their effect on the Team Foundation Server Proxy configuration.Team Foundation Server Proxy Config NodesThe following XML nodes are found in the Team ...

Info on merging and branching

Hi, I'm Chris.  I'm the new documentation manager for Team Foundation.  This post is dedicated to helping you get more familiar with merging and branching Team Foundation Server projects. Let us know what more we can post for you.-Chris...

Understanding Branching

Branching is a feature that allows a collection of files to evolve in two or more divergent paths. Branching is frequently used when teams have to maintain two or more similar code bases, as can occur when a product is released and work must begin on the next version.Branching in Team Foundation source control is analogous to a file system ...

Understanding Merging

Merging is the process of combining the changes in two distinct branches. A merge operation takes changes that have occurred in the source branch and integrates them into the target branch. Merging integrates all types of changes in the source branch including name changes, file edits, file additions, and file delete and undelete changes. If ...

Get started understanding and using Team Foundation

This post is dedicated to getting you more familiar with some of the features that make up Team Foundation. These basic concepts include information to get you started using, Team Foundation Server, the team project portal, process guidance, source control, work items, team projects, and a golden gem for figuring out what all you need to do to...

Getting Started with Team Foundation

Team Foundation is a set of tools and technologies that enable a team to collaborate and coordinate their efforts on building a product or completing a project. Team Foundation enhances team communication, tracks work status, supports team roles, enacts the team process, and integrates team tools.CollaborationThe primary purpose of Team ...