In TFS 2012 the product team introduced the concept of Teams into TFS. Before this many organisations created multiple Team Projects and now want to merge Team Projects into one, or at least fewer. There are many reasons you might have done this in the past but there is no reason to live with this.
When you are doing a Source Control migration using the TFS Integration Platform you receive a “unable to find a unique local path” runtime conflict.
Are you worried that you will not be able to migrate from http://tfs.visualstudio.com when they start charging for it and you don’t want to pay? Fear not as we have the technology to migration from TF Service to TF Server with the TFS Integration Platform.
Immediately after configuring the TFS Integration Tools you receive a TFS WIT invalid submission conflict type that states that the source item is invalid.
If you change the WorkSpaceRoot in “C:Program Files (x86)Microsoft Team Foundation Server Integration ToolsMigrationToolServers.config” you may get an access to path is denied when manually resolving conflicts as per TFS […]
If you say my post on “TFS Integration Tools – Issue: TF10141 No Files checked in as a result of a TFS check-in failure” which I just updated you will […]
If you encounter a TFS check-in failure conflict type and you try the first option of “Retry the action”. Figure: This conflict is generated during the final checkin. The migration […]
According to TFS Integration Tools – March 2012 Release there was a fix for “Resolving VC namespace conflicts results in System.InvalidOperationException: Sequence contains no elements” in the March release. I […]
TFS Integration Tools – Issue: TF205022: The following path contains more than the allowed 259 characters
You get error “TF205022: The following path contains more than the allowed 259 characters” when trying to migrate over some folders. Figure: TF205022: The following path contains more than the […]
TFS Integration Tools – Issue: TF14009: Cannot merge source into target because the target is underneath source
If you are moving source from one team project to another (I am doing a migration of Source Code from “TeamProjectA” to “TeamProjectBTeamProjectA” in the same collection) you can get […]