Menu
Steve tells me that VC 2015 and VC 2017 are actually (gonna be) binary compatible.
I found zero info wrt. this in the release notes for 2017 (RC) - or pretty much anywhere for that matter, so here goes:
Visual Studio 2017 (v141) and Visual Studio 2015 (v140)? (*)(*): Yeah, I actually went ahead and installed the 2017 RC, and from what I can see on the surface, at least the identical MSVCRT is used, that is msvcp140.dll and vcruntime140.dll (despite the platform toolset being called "v141".
562
The goal of the Microsoft Visual C++ 2015-2019 Redistributable Package is to download all of the runtimes in one package. As you can tell by the name, the package includes all of the runtimes from 2015-2019 and should be backward compatible with all apps and games created with Microsoft Visual C++.
The Microsoft C/C++ for Visual Studio Code extension supports IntelliSense, debugging, code formatting, auto-completion. Visual Studio for Mac doesn't support Microsoft C++, but does support .
In versions of Visual Studio 2019 before version 16.11, /std:c++latest is required to enable all the compiler and standard library features of C++20. For a list of supported language and library features, see What's New for C++ in Visual Studio.
Microsoft's Visual Studio IDE has added support for the C11 and C17 C language standards, thus expanding the IDE's previously limited support for C. C11 and C17 become supported language versions starting with Visual Studio 2019 16.8 Preview 3, which was released September 14.
Yes, the 141 and 140 libraries are almost identical. The version was bumped for a side-by-side issue. The v140 toolset in VisualC++ 2015 and v141 toolset in VC++ 2017 are binary compatible.
129
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
