Add an existing folder to Team Foundation Server 2010 that already exists for another Team Foundation Server 2012

Question

I work with the central Team Foundation Server (2010), and I connect to it from my workstation. On my workstation, I use both Visual Studio 2010 and 2012. I have both Team Explorer 2010 and 2012 installed, as well as the latest fixes and fixes.

I need to use Visual Studio 2010 and 2012 because I am developing both .NET 4.5 and SQL Server Reporting Server reports for SQL Server 2012.

I can configure both instances of Visual Studio to connect to TFS, I have mapped my workspace in Visual Studio 2012, and I can interact with Source Control. I tried to configure Visual Studio 2010 to use the same working folder, I can connect to TFS, I can see the source folder, but when I try to map it to the same local folder, I get the following error message:

Map

The working folder "C: \ TFS \ Example" is already used by the JohnDoesPC workspace; Dow, John on JohnDoesPC

I tried to configure the display of the workspace in the drop-down list in the source explorer:

• Team Explorer> project > Source Control > Map window> (Set local folder)

And I tried it through the "Source Control" menu in the "File" menu:

2. Go File > SourceControl > Manage Workspaces > (Select my workspace)> Edit > Try adding an existing folder.

What am I missing? Do I need to map the solution folder to two different local folders? That would be very confusing and uncomfortable!

The easiest way to say that I want two versions of TFS to point to the same local location. Is it possible? Or should I create a new project for SSRS reports only?

EDIT: See pic for more details:

Answer 1

Verify that the same workspace name is selected in Visual Studio 2010 and Visual Studio 2012. If you don’t see the 2012 workspace in Visual Studio 2010, check out the advanced workspace options in 2012. Verify that the workspace type is set to the server .

When both versions of Visual Studio use the same workspace name, they must also see and use each other's file associations.

Here's what the settings look like in 2012:

And this workspace should be visible in 2010:

Make sure that you select the same workspace name in both versions of Visual Studio: