Share via

Does Visual Studio 2017 come with Visual C++ 14.1 or 14.10?

  • Article

Question

Friday, October 6, 2017 5:07 PM

This is confusing me. The Visual Studio update VS2017 comes with v141 which is as far as I can see 14.10.xxxxx but it is referred to in various places on the internet as version 14.1. Shouldn't it be 14.10?

All replies (5)

Friday, October 6, 2017 6:41 PM

Visual Studio 2017 Update 3 actually bumps this version to 14.11.xxxxx, of course to make this more interesting, the C++ compiler version id 19.11.xxxxx.

This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.

Monday, October 9, 2017 8:05 AM

Hi popchoc,

Welcome to MSDN forum.

When you install Visual Studio it creates a file, %VCINSTALLDIR%\Auxiliary\Build\Microsoft.VCToolsVersion.default.txt, that contains the version string for the default version of the Visual C++ tools. For the previous version of vs2017, it should be 14.10.xxxx.

Visual C++ Toolset and Libraries

  • The Developer Command Prompt for Visual Studio (and the Visual C++ Command Prompt) have added support for initializing a command-prompt environment targeting the Visual C++ 2015 Toolset (v140) via the -vcvars_ver=14.0 argument.
  • Visual C++ Redist file directories have been renamed to Microsoft.VC141.* to match versioning with the toolset (14.1x). In Visual Studio 2017 RTM, these directories were incorrectly named Microsoft.VC150.*.
  • Visual C++ File Version and Directories (Visual Studio 2017 15.3) :
    • VC++ Toolset File Version : 14.11.25506.0 or 19.11.25506.0
    • VC++ Tools Directory : VC\Tools\MSVC\14.11.25503 (directory location was locked in a Preview release)
    • VC++ Redist Directory [a] : VC\Redist\MSVC\14.11.25325 (All runtimes except for MFC and OneCore)
    • VC++ Redist Directory [b] : VC\Redist\MSVC\14.11.25415 (MFC and OneCore runtimes)

refer: https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes

Best regards,

Joyce

Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Tuesday, October 10, 2017 7:55 AM

Hi popchoc,

What’s your VS 2017 version? Please check this blog: Compiler Tools Layout in Visual Studio 2017 and we can know the following:

  1. For VS 2017 RC, that version number is 14.10.24629.
  2. For VS 2017 RTM version, we can find the file: %VCINSTALLDIR%\Auxiliary\Build\Microsoft.VCToolsVersion.default.txt to know the default toolset installed with VS. In my VS 2017 15.3.3 and 15.3.5, it’s version is 14.11.25503 as below:

Best regards,

Sara

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

Saturday, October 14, 2017 5:55 AM

Thanks for that information. What I need to know is what is the appropriate way to refer to it. Do you call it 14.1 or 14.10 or 14.1x or what? I am working on updating some batch files for the new build system and in the batch files it refers to Visual Studio versions like 

    set VC_VER=9.0
    set VC_VER=10.0
    set VC_VER=11.0
    set VC_VER=12.0
    set VC_VER=14.0

so basically I want to know how to refer to Visual Studio 2017. I'm thinking about calling it VC_VER=14.1 since there's 14.10.xxx and 14.11.xxx versions. Is that acceptable?

Monday, October 16, 2017 8:42 AM

Hi,

Thank you for the update.

please have a look at here: https://stackoverflow.com/questions/31885337/what-compiler-is-in-visual-studio-2015?noredirect=1&lq=1

you can call it VC_Ver=14.1

Best regards,

Joyce

Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].