Skip to main content

TFS Integration Tools v1.0 released

The TFS Integration Tools got it first fully supported release. It’s a project developed by the Team Foundation Server (TFS) product group and the Visual Studio ALM Rangers to integrate with third party systems for migration and synchronization of data. 

What’s in the package?
  • TFSMigrationShell … This is the primary tool in the Integration Tools, and provides the ability to create, edit and run migrations from a GUI
  • MigrationConsole … Provides a command line tool for running migrations
  • ServerDiff … Compares version control files or work items on two servers that are participating in a migration or synchronization session
  • CQMigrationConfigGenerator … Extracts the CQ record type schema information, and generates a default matching TFS WITD, a field mapping, and a list of CQ users
  • TFSIntegrationAdmin … Command line utility for various management and administrative tasks such as import/export of configurations, deleting sessions and configuring service accounts
  • SyncMonitorConsole … The SyncMonitorConsole determines the number of backlogged items and time of any backlog in the processing of a continuous sync session and stores the data in the LATENCY_POLL table of the TFSIntegrationPlatform database. You can use the "TFS Integration - Latency.rdl" located at "Microsoft Team Foundation Server Integration Tools\Reports\"to report on this data.

It also contains a big list of adapters out of the box and it’s very easy to create your own:

  • ClearCase Detailed History … Provides the ability to migrate source control items between an IBM ClearCase and TFS system using the native ClearCase API. This adapter migrates all history.
  • ClearCase Selected History … Provides the ability to migrate source control items between an IBM ClearCase and TFS system using the native ClearCase API. This adapter migrates a subset of the history based on a specified label or view.
  • ClearQuest … Provides the ability to migrate work items between an IBM ClearQuest and a TFS system using the native ClearQuest API.
  • File System for TFS 2008 … Provides the ability to migrate files from a file system hierarchy into TFS 2008 version control.  This adapter can be used when there is not a direct adapter available, by exporting revisions from the source system into the file system.
  • File System for TFS 2010 … Provides the ability to migrate files from a file system hierarchy into TFS 2010 version control.  This adapter can be used when there is not a direct adapter available, by exporting revisions from the source system into the file system.
  • Proof of Concept … Provides a sample project for creating an adapter for the Integration tools.
  • SharePoint VC … This is a sample adapter that is used to migrate documents between SharePoint and TFS version control.
  • SharePoint WIT … This is a sample adapter that is used to migrate tasks between SharePoint and TFS work item tracking.
  • TFS 2008 VC … Provides a native integration point with TFS 2008 version control, using the public TFS 2008 API.
  • TFS 2008 WIT … Provides a native integration point with TFS 2008 work item tracking, using the public TFS 2008 API.
  • TFS 2010 VC … Provides a native integration point with TFS 2008 version control, using the public TFS 2010 API.
  • TFS 2010 WIT … Provides a native integration point with TFS 2008 work item tracking, using the public TFS 2008 API
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more