I only wish Visual Studio retained the same MVCRT/MSVCP runtime libraries, or at least some backward-compability mechanism. It really boils down to this - if y

I only wish Visual Studio retained the same MVCRT/MSVCP runtime libraries, or at least some backward-compability mechanism. It really boils down to this - if you do plugin development for a product (Adobe's, Autodesk, etc.) or ffi-bindings for some language or environment, then you have to make sure you use the same CRT version as the host application. And while statically linking to your CRT in your plugin DLL might work, it might not always - hopefully most people have found workarounds - for example not exposing "FILE*" or memory allocations/deallocations across DLL boundaries - e.g. alloc/free is done from the same DLL. But sometimes things like C++ exceptions make this even harder. And now I'm seeing VS2013 brings yet another new CRT. Oh bummer!