Supported operating system: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows XP Supported operating system: Windows 10, Windows 8.1, Windows 8 Microsoft Team Foundation Version Control Windows Shell Extension Supported operating system: Windows 10, 8.1, 7 SP1 Team Foundation Version Control for TFS and VSTS Supported operating system: Windows 10, Windows 8.1, Windows 7 SP1 *) VsCode Azure Repos extension is now deprecated. Team Explorer 2017 or Team Explorer Everywhere Supported operating system: Windows 10, Windows 8.1, Linux, Mac Supported operating system: Windows 10 1703+, Windows 8.1, Windows 7 SP1 If you also want to install the Team Foundation Server Power tools to match your Visual Studio/TFS version, check out this separate post. In addition to it, this post also lists the required hotfixes to make everything work.

Microsoft has an official Client Compatiblity matrix. If you've previously installed any of the packages you'll need to uninstall them first or repair all packages in the order listed. Note that for many of the items listed below, the order of installation is important.

Whether connecting to Azure DevOps or TFS (and which version).

The following variables make up what you need to install in order to be able to connect: Team Explorer ships with Visual Studio in recent versions, but in older versions it was a separate installation. To connect your IDE to Azure DevOps you usually need to make sure you have Team Explorer or an extension to your IDE installed. Even if you're using a more recent IDE, you could need one or more hotfixes and/or service packs. I sincerely hope these people store their sources securely, because these old IDEs and codebases will be causing them enough headaches.

Visual Studio has been around for a long time and there are still people developing in Visual Basic 6 or Visual Studio 2008. Formerly Visual Studio Team Services (VSTS), Visual Studio Online (VSO) and Team Foundation Service.

Visual studio version control