Skip to main content

Team Foundation Server 2012 and Visual Studio Compatibility

After upgrading our internal Team Foundation Server environment to the 2012 version, I got a lot of questions from our development teams about compatibility with different Visual Studio versions.

To help them(and you) here is the compatibility matrix(the full matrix for all TFS versions is available here):

Clients and tools Team Foundation Server 2012
Visual Studio 2012 or Team Explorer 2012 Yes
Visual Studio 2010 or Team Explorer 2010 Yes (1)
Visual Studio 2008 or Team Explorer for Visual Studio Team System 2008 Yes (2)
Team Explorer for Visual Studio 2005 Team System No (3)
Team Web Access for Team Foundation Server 2010 Not applicable
Team Web Access for Visual Studio Team Foundation Server 2012 Yes
MSSCCI 2008 No
MSSCCI 2010 No
MSSCCI 2012 Yes (4)

Important notes about Compatibility:

  1. Visual Studio Team Explorer 2010 needs this patch to connect TFS 2012
  2. Visual Studio Team Explorer 2008 needs this patch to connect to TFS 2010
  3. Visual Studio Team Explorer 2005 cannot connect TFS 2012. Visual Studio 2005 can be connected to TFS 2012 using MSSCCI Provider.
  4. The Microsoft Source Code Control Interface (MSSCCI) Provider 2012 power tool supports Visual Studio Team Foundation Server 2012. For more information, see Microsoft Source Code Control Interface (MSSCCI) Provider 2012 Power Tool.
Labels:

Popular posts from this blog

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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more