Use Visual Studio 2012 and compile with older platform toolset?

Question

The problem

I\'m using Visual Studio 2012 to develop C++ DLLs. On some machines these DLLs can not be loaded, because the platform toolset, which is

Answer 1

well it depends what you are trying to build. Some things are maybe supported via installing Windows SDK 7.1. see this post, same question, but if your project is dependent upon MFC then unfortunately it looks like it's not possible at all, mainly because nothing but VS2010 is deploying the MFC libraries.

Answer 2

According to this page on MSDN, you need to have the corresponding version of Visual Studio (2008 or 2010), or the relevant Windows SDK for the "Platform Toolset" drop down to list those versions:

To change the target platform toolset, you must have the associated version of Visual Studio or the Windows Platform SDK installed.

You also seem to be a little bit confused between "Platform Toolset", which controls which compiler/linker/etc. is used to build your application, and "Visual C++ Redistributable", which is needed to run your application. You can't install a "Platform Toolset" on a user's PC, and nor will you make one available by installing a particular "Visual C++ Redistributable" on your development PC.

Also, as far as I know, the Visual C++ Redistributable doesn't include the MFC runtimes. They're available as a separate MSI merge module (MSM).

Answer 3

A hint for the internet archive. (I cannot comment the statements above, I don't know why)

To use the v90 platform toolset (=Visual Studio 2008) in a newer Visual Studio (I testet 2013 and 2015) you need to install Visual Studio 2008 and additionally Visual Studio 2010, because the vs90 platform toolset definitions in the MS Build programs folder are part von Visual Studio 2010.

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\PlatformToolsets for v90 and v100

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0

for V110 V120 and V140

representing Visual Studio Versions: v90=2008, v100=2010, V110=2012, V120=2013, V140=2015.

After the Installation vob VS2010 the newer Visual Studio 2013 and 2015 Versions could use the vs90 and vs100 platform toolsets. (This works immidiadtly without a new installation of Visual Studio 2013/2015.) I guess Visual Studio 2012 is doing it the same way like VS2013 and VS2015.

Answer 4

I'd like to share some information, which I came across and figured out how to use them for my purpose.

Apparently it is a good option to use static linking. It didn't always work for me, but for a smaller project of mine, it works quite good. And the result is a DLL with no dependencies other than kernel32.dll and the like.

Simply use /MT for release configuration and /MTd for debug and you'll be fine.

The problem here is that a developer like me gets the current Visual Studio version, shortly after its release, but you can't really expect common users to have runtimes installed which are only a few weeks old. And installing different versions of Visual Studio just to use the old runtime is definitely not what you want.