There's no need to recompile with a matching toolset. You can still use them in an application built by Visual Studio 2017 or 2019.
Say you have third-party libraries built by Visual Studio 2015.
It's reflected in the C++ toolset major number, which is 14 for all three versions. The runtime libraries and apps compiled by any of these versions of the compiler are binary-compatible. Quoting Microsoft from C++ binary compatibility between Visual Studio 2015, 2017, and 2019: Yes, for certain values of "and so on" -) The 2015, 20 redistributables are binary compatible with the most recent release thereof. The 2017 redistributable replaces the 2015 one, and so on Trying to find out such info from online resources is like looking for a needle in a haystack. And one of our support staff has already identified that that sometimes won't install if the 2005 SP1 runtime is missing. My second question is a bit more generic and I don't really expect many answers to that one but.Īre there any well known 3rd party developer tools that you know are using one of the four Redistributables mentioned in my list above? For example, we use Crystal Reports runtime 13.0.17 - oh how I wish we could dump that and move on.
I see many resources online claiming that, for example, the 2017 redistributable replaces the 2015 one, and so on but does that backward compatibility go all the way back to the 2005 SP1 version? It would be great if I could just tell them "look, just install VC++ redistributable version xyz and anything that needs one of the above four builds will work just fine" Relieve the pressure on our support staff to install all these components as well as our software when setting up machines for first use. Ideally I would just like to chuck 'em all. So I'm starting to think a lot of the above are no longer necessary. And I'm finding that as I install our software on systems without installing the above first most of our applications are working perfectly normally without errors. Microsoft Visual Studio C++ 2012 Redistributable - build 0īut as the years have gone on many of the 3rd party components we used have been replaced with newer and better ones, and we include them to our Projects through NuGet. Microsoft Visual Studio C++ 2010 Redistributable - build 9 Microsoft Visual Studio C++ 2008 Redistributable - build 9.6161
This has led to us distributing as part of our initial installation process: Microsoft Visual Studio C++ 2005 Redistributable (SP1) - build 1 Also, historically, these tended to come with various dependencies on Microsoft Visual Studio C++ runtime versions. NET Framework but historically we have had to include a number of 3rd party components. I've been looking around and I'm not sure I see a clear answer to this so I'm sorry if this has been asked before my "Google-Fu" is failing me.
0 kommentar(er)
