visual-c++-2017

This SO post: Is Visual-C++-2017 binary compatible with VC++-2015? clearly says that VS 2017 is binary compatible with VS 2015. It even looks like the official position. My question is, in the past, I distinctly remember running into linker errors (I do not recall the specific set of errors) every time I try to link in a static library that was compiled with a different version of MSVC into an EXE that is being built with a newer version of MSVC. Yet, binary (in)compatibility sounds like something that will blow up in your face at runtime , not link time. Can someone tell me if previous

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: Is a C++ (C++ interface) DLL built with VC++-2017 binary compatible with a DLL built by VC++-2015? Do 2017 and 2015 use the same (dynamic) runtime library ? If so, what, if any, is the runtime difference between Platform Toolset 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

With Microsoft changing the pattern of registry entries in its latest versions, how do i detect if Visual C++ 2017 Redistributable is installed on a machine? My aim is to install VC++2015Redist since the software is written using VS2015. If i can successfully detect VC++2017Redist on a machine, then I skip my installation of VC++2015Redist The 2017 VC++ Redistributable installation upgrades/REPLACES the 2015 installation Installation of the Visual Studio 2017 Redistributables upgrades and replaces any existing installation of the 2015 Redistributables. I've checked this, and the 2015