Azure DevOps Blog

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

Moving a Team Project from One Version to the Next

If the team project you are managing has completed a major iteration or milestone, and has grown too large or is not compatible with the desired workflow going forward, you can create a new team project based on the existing one. Moving a team project from one version to the next involves some combination of branching source code, copying ...

Team Foundation Server Data Warehouse

The data warehouse is a relational database organized in a star schema with an OLAP database derived from that database. The OLAP database allows the reporting tools to access the derived information without degrading the performance of the relational database that actually stores the real-time information from the clients.The warehouse stores...

Team Foundation Server Permissions

Mike writes: "We need to configure the server to grant all users the ability to create a Team Project and manage the users of that specific project. However, a user must not be allowed to delete/modify/access a project which he or she does not belong to. Also, since users will belong to the Sharepoint administration group and SQL Server ...

Team Foundation Server Default Groups, Permissions, and Roles

When you create a new project in Team Foundation Server, new project-level groups are created for that project, by default, and are assigned permissions to access resources appropriate to that group. To customize projects to better suit your business needs, you must understand what permissions are assigned to which users and groups by default...

Team Foundation Server Permissions

Authorization for user actions, such as workspace administration and project creation, are determined by permissions. When you create a project in Team Foundation Server, four default groups are created for that project regardless of your choice of process template. By default, each of these groups has a set of permissions defined for them ...

Migrating from Visual SourceSafe to Team Foundation Source Control

In response to a request for information from Earl dated 12/22/05 asking: "Do you have any documentations regarding migration of the VSS6 to Team System...?  We have two thorough walkthroughs on this two step process; preparation and then migration. Thanks for the request Earl.-Lisa...

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...