Sorry it took a bit longer to get these out than we expected. The landing page that link points to includes lots of info about compatibility, changes, etc. I strongly suggest you to bookmark that link, because it can really save you when you have old client (like VS 2010, VS 2012) that experiences difficulties connecting to the newest version of TFS / VSTS.Today we released the TFS 2015 Power Tools that accompany VS 2015 and TFS 2015. This link will specify you all service pack and patch you need to install to connect to various version of TFS. This sequence of steps is taken from the Exceptional link of Jesse Houwing.

Visual Studio 2010 Compatibility Update for Windows 8 and Visual Studio 2012.

Visual Studio 2010 GDR for Team Foundation Service.

For VS 2010 to connect to VSTS / TFS 2017 these are the steps you need to take.

This error happens because you lack some required update to connect to TFS 2017 from VS 2010. The user name is not a fully-qualified name, parameter name workspaceOwner As an example you can receive the following error when you try to connect to TFS 2017 TFVC repository from VS 2010. Keeping your TFS updated will guarantee that you can use TFS with newer and older tooling (yes, even Visual Basic 6 can work with TFS 2017)īut even if the compatibility matrix confirm that you can use VS 2010 to connect to TFS 2017, you probably need to install some additional software, to guarantee the connection. This means that new version of Visual Studio could have problem connecting to older instances of TFS. Microsoft ensure that old tools (like VS 2010) always can connect to latest version of TFS, but the opposite is not true. One of the reason why I always suggest of keeping TFS upgraded is the compatibility matrix.

Tfs client tools 2010