Just a quick note that your libraries provided with SilverLining and Triton are all binary-compatible with applications built with the recent Visual Studio 2019 release.

Both Visual Studio 2017 and Visual Studio 2019 are compatible with libraries built with Visual Studio 2015. If you are using Visual Studio 2015, 2017, or 2019, the libraries under our “VC14” directory will work. Technically, Visual Studio 2015 is version 14.0, 2017 is 14.1, and 2019 is 14.2 – they are all binary-compatible, so there’s no need for us to make our SDK even larger than it is by providing libraries for each specific version.

There is one caveat – certain versions of Visual Studio 2017+ cannot link in VC140 libraries when “whole program optimization” and “link-time code generation” is enabled. If you encounter errors surrounding too-old libraries with Triton or SilverLining when using the VC14 libraries, disable these options in your project settings. You’ll find them under C++/Optimization and Linker/Optimization – just set “whole program optimazation” to off, and “link-time code generation” to default, and you should be back in business.

Of course, if you have a full source license, you can build our libraries yourself for whatever toolchain you want. But there shouldn’t be any real need to do so.

So, feel free to upgrade Visual Studio if you’re so inclined – there shouldn’t be any issue with our products. Just continue to use our VC14 libraries.