I also have this gripe - why every version of Visual Studio has to change so much drastically the CRT version, thus requiring new DLL and breaking all plugins that happen to be linking to some other version.
This basically means, if you are using (say) Autodesk products, you have to compile all your plugins with exactly the same version the main product (exe) was compiled.
This is absolute mess. Talk about 7 different MSVCRxx.DLL and MSVCPxx.DLL in one process.
Why can't you think of scheme where backward compatibility works for the CRT/C++RT too?
Oh, and on naming things - please stick with VS2012 -> CRT2012 if possible.
Also why ShortName / PlatformName in VisualStudio is named so crazy - one amd64/x64 vs Win32/x86 - and then SDK's coming from Microsoft would place in the lib/ folder things sometimes with lib/$(ShortName) and sometimes with lib/$(PlatformName).
I know why - because these things are not important. Just hard-code it in your .vcxproj and live a happier life :) Automation begone!
This basically means, if you are using (say) Autodesk products, you have to compile all your plugins with exactly the same version the main product (exe) was compiled.
This is absolute mess. Talk about 7 different MSVCRxx.DLL and MSVCPxx.DLL in one process.
Why can't you think of scheme where backward compatibility works for the CRT/C++RT too?
Oh, and on naming things - please stick with VS2012 -> CRT2012 if possible.
Also why ShortName / PlatformName in VisualStudio is named so crazy - one amd64/x64 vs Win32/x86 - and then SDK's coming from Microsoft would place in the lib/ folder things sometimes with lib/$(ShortName) and sometimes with lib/$(PlatformName).
I know why - because these things are not important. Just hard-code it in your .vcxproj and live a happier life :) Automation begone!