RE: [INTERNALS-WIN] Re: VC15 or VS2017?

Hi Jan, > -----Original Message----- > From: Jan Ehrhardt [mailto:phpdev@ehrhardt.nl] > Sent: Wednesday, April 26, 2017 4:52 AM > To: internals-win@lists.php.net > Subject: [INTERNALS-WIN] Re: VC15 or VS2017? > > Jan Ehrhardt in php.internals.win (Wed, 26 Apr 2017 03:53:22 +0200): > >Wouldn't it be that Microsoft gradually drops the VC-numbering? We are > >calling Visual Studio 2017 VC15, but what is the ground for that? > > Is it just an abbreviation for Visual C/C++, version 15? Then we are at > VC15.1 right now: > > https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes > > Excerpt from the 'About' in the VS2017 IDE: > > >Microsoft Visual Studio Community 2017 Version 15.1 (26403.7) Release > >VisualStudio.15.Release/15.1.0+26403.7 > > > >Visual C++ 2017 00369-60000-00001-AA847 > >Microsoft Visual C++ 2017 > > Visual Studio says it is version 15.1, but Visual C/C++ and C# use the '2017' as > denominator. VS15 and VC2017 come to mind. > > Visual Studio 15, Visual C/C++ 2017 and toolset v141. Confusing all over. > > Even the development team suffered by it. Daniel Griffing in > > https://developercommunity.visualstudio.com/content/problem/5068/when- > installing-visual-studio-2017-rc-with-uwp-dev.html?childToView=14493# > > >The fact that we temporarily shipped a 'v150' Platform Toolset in early > >Visual Studio "15" Previews was an unfortunate artifact of us working > >through our versioning plan. For Visual Studio 2017 RC, there is no > >'v150' Platform Toolset "By Design". When I look at paths like this C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Redist\MSVC\14.10.25008\x64\Microsoft.VC150.CRT so it appears it still calls CRT vc15. It might be mistake or not, vcXX is what we use for the shortcuts and the name is what one sees explicitly here.. 14.10 is the toolset version, 1910 is compiler version, etc. We always refer to the runtime version. Regards Anatol