TFS 2012 Issue: Get Workspace already exists connecting with VS 2008 or VS 2010

Issue

When you have VS 2008 or VS 2010 installed as well as VS 2012 and you are connecting to TFS 2012 you my get an error the first time that you connect:

image
Figure: The Workspace already exists on computer

This results in this error ever time you start VS 2010 or VS 2008.

Applies to

  • Visual Studio 2008 connecting to Team Foundation Server 2012
  • Visual Studio 2010 connecting to Team Foundation Server 2012

Finding

If Visual Studio 2012 is the first thing that you open to create a new workspace against a new collection a default workspace of “computername;username” will be created as a “Local” workspace.

When you subsequently open VS 2008 or VS 2010, which do not support Local Workspaces, you get this error when it tries to create a workspace. Visual Studio does not detect that this workspace already exists as when it queries the server the “agent” filtering does not return local workspaces.

Workaround

Manually create a “Server” workspace for use in VS 2010 and VS 2008.

image
Figure: Create a new Workspace with a new Name

  1. Select “File | Source Control | Workspaces… | Add…”
  2. Fill out a new name and then select “OK”
  3. Select your new Workspace from the drop down

You can now connect to Source Control..

About the Author:

10 Comments

  1. […] TFS 2012 Issue: Get Workspace already exists connecting with VS 2008 or VS 2010 […]

  2. […] TFS 2012 Issue: Get Workspace already exists connecting with VS 2008 or VS 2010 […]

  3. ALM Links–07/20/2012 » ALM Rocks! July 20, 2012 at 4:11 am

    […] TFS 2012 Issue: Get Workspace already exists connecting with VS2008 or VS2010 […]

  4. […] TFS 2012 Issue: Get Workspace already exists connecting with VS 2008 or VS 2010 […]

  5. rtorrone December 18, 2012 at 2:17 pm

    Hi Martin – I can’t be the only one who used this great blog post. I had to close VS 2008 and reopen it after I added the new Workspace to be able to select it from the pull down (last step) but after that it worked fine. You’re Terrific! Thank you very much. Richard Torrone (from Joisy)

  6. Sumit Supalurs February 19, 2013 at 10:03 am

    Thank you very much for your guide.

  7. Ricardo Serradas September 17, 2013 at 10:05 am

    Hello! Great post! But there’s a problem with this entire scenario: what if I need to use the same working folder with both workspaces (ex.: C:tfscollection1)? I’m unable! TFS does not allow two workspaces to map the same local folder 🙁

    This solution only applies if I use different mappings. Here in my case, I use to map the root of the collection to a folder. This collection has projects both in VS 2008 and in VS2012… Did you get it?

    So, I had to make my local workspaces server workspaces again.

  8. KeyboardG February 10, 2016 at 2:00 pm

    This just avoids the problem and doesn’t fix anything.

  9. Geovanny Morillo May 10, 2017 at 8:58 am

    This also happens with 2017

  10. Daniel Cairns August 1, 2017 at 6:24 am

    Thanks!

Leave A Comment