![]() ![]() Sometimes, despite best efforts, adding new functionality can introduce bugs that affect your code. The source changes that we document are almost always forward and backward compatible, meaning that you can compile the code with either a new or old compiler. We test all source changes for compatibility and document all C++ conformance changes and any required source changes with every release. Minor version updates are designed to be source and binary compatible with previous versions. (Note that for historical reasons the MSVC compiler version is 5 higher than the MSVC toolset version displayed in Visual Studio.) Visual Studio Version For reference, here are the MSVC toolset versions and compiler versions ( _MSC_VER) in each release of VS2015 to VS2017. ![]() The MSVC toolsets in 15.1, 15.2, and 15.4 were incremental, bug fix-level updates. We’re making another significant update with VS2017 version 15.5. We’ve made significant updates to the MSVC toolset twice so far in VS2017: once with the first release of VS2017 and again in update version 15.3. Even though the MSVC compiler toolset in VS2017 delivers many new features and conformance improvements it is a minor version, compatible update from 14.00 in VS2015 to 14.10 in VS2017. This minor version bump indicates that the VS2017 MSVC toolset is binary compatible with the VS2015 MSVC toolset, enabling an easier upgrade for VS2015 users. The MSVC toolset in VS2017 is built as a minor version update to the VS2015 compiler toolset. Since its first release in March we’ve released four major updates to VS2017 and are currently previewing the fifth update, VS2017 version 15.5. We’ve been delivering improvements to Visual Studio 2017 more frequently than ever before. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |