See this post for some notes as this means you are again using the Windows 7.1 SDK rather than the Windows 8.x SDK with the _xp toolsets. You have to use v140_xp Platform Toolset instead. The v140 toolset does not support targeting Windows XP / Server 2003. VS 2010 and the v100 toolset supports targeting Windows XP and Windows Server 2003. It's particularly important for Windows desktop apps that you set the _WIN32_WINNT preprocessor define for your target platform as the Windows 8.x SDK does not default to the 'oldest supported platform' like earlier Windows SDKs did. There's been a lot of change there too particularly for DirectX development.

Since you are jumping three major releases at once-and about 10 minor updates-, it can be a bit overwhelming especially working through all the new warnings.Īnother thing to keep in mind is that Visual C++ 2010 used the Windows 7.1 SDK, while Visual C++ 2012 or later use the Windows 8.x SDK. Keep in mind that Visual C++ 2010 used the C++0x Draft Standard, and Visual C++ 2015 meets the C++11 Standard with the exception of Expression SFINAE (which is partly there in Update 1), so quite a bit has changed in the intervening years including some breaking changes. v140) are not installed by the Typical installation option. One major change in VS 2015 is that the C++ tools (i.e. The VS 2015 custom install options will let you install the v120 Platform Toolset, but not the v110 or v100 Platform Toolsets. You either install VS 2010 and build your project, or better yet you upgrade your projects.

Visual studio build tools 2019