Getting “Failed to create mapping” when adding TFS source control solution

Question

I created a new Team Project in TFS, but when I try to add my solution to it, I get:

'Failed to create mapping

It is not possible to map the server path, $ / Finance / MyApp, because it is not implemented under a team project.

I can’t find anything in google or here that looks remotely like this problem.

Answer 1

I had this problem when using the Microsoft Team Foundation Service from Visual Studio 2012. I just created a new team project through the TFS website. Although I could see my new project in the “add solution” window, I received an error message reported by OP.

I had to go to the "Team Explorer" window, then to "Connect to Team Projects" and mark the new project. Then I was able to add my solution to the team project.

Answer 2

Is a financial project for you?

If not, you can clear the mappings for the workspace or simply delete the workspace. http://msdn.microsoft.com/en-us/library/54dkh0y3(v=VS.100).aspx

Answer 3

Had the same problem when upgrading a project to TFS 2010 from 2008. The solution was to delete the vsssc file in the project root folder and re-add it

Answer 4

In my case, I had to make Team Explorer and connect to a new project, then I had to close my solution and reopen it, and then “add to the original control”.

- Connect and verify the project in the command explorer window - Close the solution - Open the solution --retry add the solution to the source control

Answer 5

I had this problem using the Visual Studio Online control, Visual Studio does not recognize the team project even after connecting to team projects, updating, restarting Visual Studio. I had to use the "Open in Visual Studio" link from a project on the Visual Studio Online site, and then open the solution.

Answer 6

Well, I didn’t want to do anything so decisive, it turned out that one of my subfolders inside the solution that I wanted to add to the original control was displayed inside another workspace (on another TFS server). So the solution was to connect to another TFS server, find and delete the conflicting folder mapping inside this workspace, and try again.

Answer 7

I had the same problem using visual studio 2008 and TFS 2012. In my case, when I manually added a local folder to the project through workspace mapping, the problem disappeared.

File -> Source Control -> WorkSpaces -> Edit

Then, when I went to add the solution to the original control, it automatically detected the mapping.

Answer 8

In my case, I copied the folder from My Documents to c: \ tfsroot, where I mapped the TFS root. Then, when I opened the solution and added it to TFS, it worked.