{"id":13155,"date":"2017-03-06T15:38:26","date_gmt":"2017-03-06T22:38:26","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/vcblog\/?p=13155"},"modified":"2022-08-11T18:38:49","modified_gmt":"2022-08-11T18:38:49","slug":"finding-the-visual-c-compiler-tools-in-visual-studio-2017","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/finding-the-visual-c-compiler-tools-in-visual-studio-2017\/","title":{"rendered":"Finding installed Visual C++ tools for Visual Studio 2017"},"content":{"rendered":"

<\/i>Content outdated<\/strong><\/p> For up-to-date documentation see Tools for detecting and managing Visual Studio instances<\/span><\/span><\/a>.<\/div>There have been a number of questions from customers about how to locate the tools in the world of this new installation model. \u00a0The following blog post will share a number of options available for locating Visual Studio 2017 instances and provides various samples that illustrates the process in action.<\/p>\n

How to find installed Visual Studio 2017 instances and C++ tools<\/strong><\/h3>\n

There are multiple ways you can go about the finding the VS instances installed and determining the tools installed for each instance.<\/p>\n

1. \u00a0vswhere.exe<\/a>:\u00a0 \u00a0A stand-alone native executable that is redistributable and can be used to locate installed Visual Studio product instances for use in build and deployment scripts. \u00a0The tool\u00a0supports emitting different formats so far including plain text, JSON, and XML.\u00a0 For example, the following batch script for vswhere will find the root path the latest installed version that also contains the C++ Desktop workload:<\/p>\n

for \/f \"usebackq tokens=1* delims=: \" %%i in (`vswhere.exe -latest -requires Microsoft.VisualStudio.Workload.NativeDesktop`) do (\r\n\r\nif \/i \"%%i\"==\"installationPath\" set dir=%%j\r\n\r\n)<\/code><\/pre>\n
%dir%<\/em> now contains the root installation path, if available.<\/p>\n
2. \u00a0PowerShell API<\/a>: This is the simplest API for finding VS installation instances and components, but of course requires PowerShell v3 and above.\u00a0 If you are running on PowerShell v3 or v4, you will need to also install\u00a0PowerShellGet<\/a>. \u00a0This is already included in PowerShell v5 that comes with Windows 10.\u00a0 The following command will list all installed VS2017 instances that also installed the v141 toolset for x86 and x64:<\/p>\n
First install the VSSetup module:<\/p>\n
Install-Module VSSetup -Scope CurrentUser<\/code><\/pre>\n
After that is completed, the following script will list all installed instances with Visual C++ compilers installed:<\/p>\n
Get-VSSetupInstance | Select-VSSetupInstance -Latest -Require Microsoft.VisualStudio.Component.VC.Tools.x86.x64<\/code><\/pre>\n
3. \u00a0Visual Studio Setup API<\/a>: This COM API allows for querying installed VS instances and their components from a variety of programming languages (C++, C#, VB).\u00a0 The code is not as simple as the PowerShell script, but we have multiple examples on GitHub of how to consume the API:<\/p>\n
Samples on GitHub<\/a> (Sample with no NuGet dependency<\/a>)<\/p>\n
Example: Finding instances with an installed Visual C++ toolset with the API<\/strong><\/p>\n
For a more specific example of using this COM API from C++ to list installed instances that include Visual C++ tools, check out this sample on GitHub<\/a>.<\/p>\n
It is inside PrintPackageReference<\/em> function that my sample checks the name of each installed component in the instance to determine if the Visual C++ toolset is installed (i.e. if \u201cMicrosoft.VisualStudio.Component.VC.Tools.x86.x64\u201d is installed).<\/p>\n
\/\/check if instance has VC tools\r\nif (bstrId == L\"Microsoft.VisualStudio.Component.VC.Tools.x86.x64\") {\r\nvcToolsFound = true;\r\nstd::wcout << L\"Instance \" << OLE2T(vcInstance) << \" contains the VC++ 2017 compiler tools (x86 and x64 targets).\\n\";\r\n}\r\n<\/code><\/pre>\n
If you build the solution, a simple command prompt will launch that can list installed Visual Studio instances, their components, and which instances have C++ tools installed.\u00a0 To find the VC++ build tools on the machine with the tool, select option #3 in and it will indicate which instance have VC++ tools installed:\"1\"<\/a><\/p>\n
Note:\u00a0 This sample is not an official tool and is meant simply to instruct how to leverage the COM API to locate the installed Visual C++ tools.<\/p>\n
\u00a0C++ installation workloads and components<\/strong><\/h3>\n
Below is a table of the underlying names used to describe each C++ workload, as well as the underlying component names used by the installer for the options provided in each workload. \u00a0The\u00a0 Visual C++ 2017 v141 compiler toolset component (x86 and x64 targeting), known as\u00a0Microsoft.VisualStudio.Component.VC.Tools.x86.x64<\/strong>, comes included in the desktop workload as a recommended (pre-selected) component and is a required (always installed) component in the C++ game and build tools workloads.<\/p>\n\n\n\n\n\n\n\n\n
Workload<\/strong><\/td>\nInstallation Name<\/strong><\/td>\n<\/tr>\n
Desktop development with C++<\/td>\nMicrosoft.VisualStudio.Workload.NativeDesktop<\/td>\n<\/tr>\n
Universal Windows Platform development<\/td>\nMicrosoft.VisualStudio.Workload.Universal<\/td>\n<\/tr>\n
Linux development with C++<\/td>\nMicrosoft.VisualStudio.Workload.NativeCrossPlat<\/td>\n<\/tr>\n
Game development with C++<\/td>\nMicrosoft.VisualStudio.Workload.NativeGame<\/td>\n<\/tr>\n
Mobile development with C++<\/td>\nMicrosoft.VisualStudio.Workload.NativeMobile<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\nBuild Tools Workloads<\/strong><\/p>\n\n\n\n\n
MSBuild tools<\/td>\nMicrosoft.VisualStudio.Workload.MSBuildTools<\/td>\n<\/tr>\n
Visual C++ build tools<\/td>\nMicrosoft.VisualStudio.Workload.VCTools<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Desktop development with C++<\/strong><\/h4>\n
\"desktop\"<\/a><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Friendly Name<\/strong><\/td>\nComponent Name<\/strong><\/td>\n<\/tr>\n
VC++ 2017 v141 toolset (x86, x64)<\/td>\nMicrosoft.VisualStudio.Component.VC.Tools.x86.x64<\/td>\n<\/tr>\n
C++ profiling tools<\/td>\nMicrosoft.VisualStudio.Component.VC.DiagnosticTools<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.14393.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.14393<\/td>\n<\/tr>\n
Visual C++ tools for CMake<\/td>\nMicrosoft.VisualStudio.Component.VC.CMake.Project<\/td>\n<\/tr>\n
Visual C++ ATL support<\/td>\nMicrosoft.VisualStudio.Component.VC.ATL<\/td>\n<\/tr>\n
Windows 8.1 SDK And UCRT SDK<\/td>\nMicrosoft.VisualStudio.ComponentGroup.NativeDesktop.Win81<\/td>\n<\/tr>\n
Windows XP support for C++<\/td>\nMicrosoft.VisualStudio.ComponentGroup.NativeDesktop.WinXP<\/td>\n<\/tr>\n
MFC and ATL support (x86 and x64)<\/td>\nMicrosoft.VisualStudio.Component.VC.ATLMFC<\/td>\n<\/tr>\n
C++\/CLI support<\/td>\nMicrosoft.VisualStudio.Component.VC.CLI.Support<\/td>\n<\/tr>\n
Clang\/C2 (experimental)<\/td>\nMicrosoft.VisualStudio.Component.VC.ClangC2<\/td>\n<\/tr>\n
Standard Library Modules<\/td>\nMicrosoft.VisualStudio.Component.VC.Modules.x86.x64<\/td>\n<\/tr>\n
IncrediBuild<\/td>\nComponent.Incredibuild<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10586.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10586<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10240.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10240<\/td>\n<\/tr>\n
Visual C++ 2015.3 v140 toolset (x86, x64)<\/td>\nMicrosoft.VisualStudio.Component.VC.140<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Universal Windows Platform development<\/strong><\/h4>\n
\"uwp\"<\/p>\n
*C++ Universal Windows Platform development tools<\/em> are required to be installed for C++ UWP development but are not<\/u> installed by default.<\/p>\n\n\n\n\n\n\n\n\n\n
Friendly Name<\/strong><\/td>\nComponent Name<\/strong><\/td>\n<\/tr>\n
IntelliTrace<\/td>\nMicrosoft.VisualStudio.Component.IntelliTrace.FrontEnd<\/td>\n<\/tr>\n
Graphics debugger and GPU profiler for DirectX<\/td>\nMicrosoft.VisualStudio.Component.Graphics.Tools<\/td>\n<\/tr>\n
*C++ Universal Windows Platform development tools<\/td>\n*Microsoft.VisualStudio.ComponentGroup.UWP.VC<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10240.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10240<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10586.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10586<\/td>\n<\/tr>\n
Architecture and analysis tools<\/td>\nMicrosoft.VisualStudio.ComponentGroup.ArchitectureTools.Managed<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Game development with C++<\/strong><\/h4>\n
\"game\"<\/p>\n\n\n\n\n\n\n\n\n\n
Friendly Name<\/strong><\/td>\nComponent Name<\/strong><\/td>\n<\/tr>\n
C++ profiling tools<\/td>\nMicrosoft.VisualStudio.Component.VC.DiagnosticTools<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.14393.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.14393<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10586.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10586<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10240.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10240<\/td>\n<\/tr>\n
Windows 8.1 SDK And UCRT SDK<\/td>\nMicrosoft.VisualStudio.ComponentGroup.NativeDesktop.Win81<\/td>\n<\/tr>\n
IncrediBuild<\/td>\nComponent.Incredibuild<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Mobile development with C++<\/strong><\/h4>\n
\"mobile\"<\/a><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Friendly Name<\/strong><\/td>\nComponent Name<\/strong><\/td>\n<\/tr>\n
Android NDK (RI 3B)<\/td>\nComponent.Android.NDK.R13B<\/td>\n<\/tr>\n
Apache Ant (1.9.3)<\/td>\nComponent.Ant<\/td>\n<\/tr>\n
Android SDK setup (API level 19 and 21)<\/td>\nComponent.Android.SDK19<\/td>\n<\/tr>\n
Android SDK setup (API level 22)<\/td>\nComponent.Android.SDK22<\/td>\n<\/tr>\n
Android SDK setup (API level 23)<\/td>\nComponent.Android.SDK23<\/td>\n<\/tr>\n
Java SE Development Kit (8.0920.14)<\/td>\nComponent.JavaJDK<\/td>\n<\/tr>\n
C++ Android development tools<\/td>\nComponent.MDD.Android<\/td>\n<\/tr>\n
Google Android Emulator (API Level 23)<\/td>\nComponent.Android.Emulator<\/td>\n<\/tr>\n
Intel Hardware Accelerated Execution<\/td>\nComponent.HAXM<\/td>\n<\/tr>\n
Android NDK (RI 3B) (32bit)<\/td>\nComponent.Android.NDK.R13B_3264<\/td>\n<\/tr>\n
Android NDK (R12B)<\/td>\nComponent.Android.NDK.R12B<\/td>\n<\/tr>\n
Android NDK (R12B) (32bit)<\/td>\nComponent.Android.NDK.R12B_3264<\/td>\n<\/tr>\n
Android NDK (R11C)<\/td>\nComponent.Android.NDK.R11C<\/td>\n<\/tr>\n
Android NDK (R11C) (32bit)<\/td>\nComponent.Android.NDK.R11C_3264<\/td>\n<\/tr>\n
C++ iOS development tools<\/td>\nComponent.MDD.IOS<\/td>\n<\/tr>\n
IncrediBuild<\/td>\nComponent.Incredibuild<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Visual C++ build tools<\/strong><\/h4>\n
\"bt\"<\/p>\n
*The Visual C++ Build tools always<\/u> installs the VS2017 v141 toolset.<\/em><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Friendly Name<\/strong><\/td>\nComponent Name<\/strong><\/td>\n<\/tr>\n
*VC++ 2017 v141 toolset (x86, x64)<\/td>\n\u00a0Microsoft.VisualStudio.Component.VC.Tools.x86.x64<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.14393.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.14393<\/td>\n<\/tr>\n
Visual C++ tools for CMake<\/td>\nMicrosoft.VisualStudio.Component.VC.CMake.Project<\/td>\n<\/tr>\n
Windows 8.1 SDK And UCRT SDK<\/td>\nMicrosoft.VisualStudio.ComponentGroup.NativeDesktop.Win81<\/td>\n<\/tr>\n
Visual C++ ATL support<\/td>\nMicrosoft.VisualStudio.Component.VC.ATL<\/td>\n<\/tr>\n
MFC and ATL support (x86 and x64)<\/td>\nMicrosoft.VisualStudio.Component.VC.ATLMFC<\/td>\n<\/tr>\n
C++\/CLI support<\/td>\nMicrosoft.VisualStudio.Component.VC.CLI.Support<\/td>\n<\/tr>\n
Clang\/C2 (experimental)<\/td>\nMicrosoft.VisualStudio.Component.VC.ClangC2<\/td>\n<\/tr>\n
Standard Library Modules<\/td>\nMicrosoft.VisualStudio.Component.VC.Modules.x86.x64<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10586.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10586<\/td>\n<\/tr>\n
Windows 10 SDK (10.0.10240.0)<\/td>\nMicrosoft.VisualStudio.Component.Windows10SDK.10240<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Setting up your command-line environment<\/strong><\/h3>\n
The Developer Command prompt in Visual Studio 2017 can be used to set the path to the VC++ toolset in the VCToolsInstallDir<\/em> environment variable.\u00a0 Now that we found have the path for each of the installed VS2017 instances that have VC++ compiler tools installed, we will refer to this directory as <VSInstanceDir><\/strong>.\u00a0 This script is in the following location:<\/p>\n
<VsInstanceDir>\\Common7\\Tools\\vsdevcmd.bat [-arch=<tgt_arch>] [-host_arch=<host_arch>]<\/p>\n
<tgt_arch><\/strong> is the architecture upon which the produced binary will run (x86 [default], x64, arm).<\/p>\n
<host_arch><\/strong> is the architecture for which the compiler\/linker was built (i.e. do you want cl.exe\/link.exe, itself, to be able to make use of 32-bit or 64-bit address space) (x86 [default], x64).<\/p>\n
Here is an example that will set up the command-line build environment to use the host-x64 compiler targeting x64, the following command would be used:<\/p>\n
<VsInstanceDir>\\Common7\\Tools\\vsdevcmd.bat -arch=x64 -host_arch=x64<\/p>\n
We have now configured our command-line build environment so that it knows where the correct VC++ tools are based on our preferences(host\/target).<\/p>\n
Identifying the VC++ compiler tools version<\/strong><\/h3>\n
In a world where multiple version of VC++ tools could be installed in a single VS instance, we have introduced the concept of <VCToolsVersion><\/strong> which indicates the default version of VC++ tools for that VS installation instance.\u00a0 If you plan to manually assemble path to the VC++ toolset directory, we need to know the default version of the installed tools to get the full path.<\/p>\n
The <VCToolsVersion> is found in one of two files that can be located once you have a <VSInstanceDir>.<\/p>\n
<VsInstanceDir>\\VC\\Auxiliary\\Build\\Microsoft.VCToolsVersion.default.[txt|props]<\/em><\/p>\n
You can check out the batch script located <VsInstanceDir>\\Common7\\Tools\\vsdevcmd\\ext\\vcvars.bat<\/em> as an example of how the VS Developer Command Prompt does this.<\/p>\n
Once a <VCToolsVersion> value is identified, the full VC++ tools path can be manually constructed as follows:<\/p>\n
<VsInstanceDir>\\VC\\Tools\\MSVC\\<VCToolsVersion>\\bin\\Host<host_arch>\\<tgt_arch><\/em><\/p>\n
For our installed tools for host-x64 and target-x64, the path looks like:<\/p>\n
<VSInstanceDir>\\VC\\ToolsMSVC\\14.10.24930\\bin\\HostX64\\x64<\/em><\/p>\n
Closing remarks<\/strong><\/h3>\n
Since we have removed the VS150COMNTOOLS registry key to support the new world where multiple VS instances of the same product can be installed side-by-side on the same machine, we know that many build systems and tools have relied on this in the past and the new options are not an identical replacement.\u00a0 We are actively working with library developers and others with builds that depend on the VC++ compiler tools, and we are open to further feedback to help refine and improve upon the solutions mentioned above.\u00a0 Please share any feedback you have in the comments or feel free to send more detailed suggestions to visualc@microsoft.com<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
There have been a number of questions from customers about how to locate the tools in the world of this new installation model. \u00a0The following blog post will share a number of options available for locating Visual Studio 2017 instances and provides various samples that illustrates the process in action. How to find installed Visual […]<\/p>\n","protected":false},"author":295,"featured_media":35994,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-13155","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus"],"acf":[],"blog_post_summary":"
There have been a number of questions from customers about how to locate the tools in the world of this new installation model. \u00a0The following blog post will share a number of options available for locating Visual Studio 2017 instances and provides various samples that illustrates the process in action. How to find installed Visual […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/13155","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/295"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=13155"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/13155\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/35994"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=13155"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=13155"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=13155"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}