title: How bad is it to mix and match Visual C++ runtime DLL files in one process?
body: <p>I have an application that is built with Visual&nbsp;Studio&nbsp;2012, and thus it depends on <code>MSVCP110.DLL</code> and <code>MSVCR110.DLL</code>. I'm using another DLL file, which seems to have been built with Visual&nbsp;Studio&nbsp;2010 and depends on <code>MSVCP100.DLL</code> and <code>MSVCR100.DLL</code>. Yet another DLL I have was build with Visual&nbsp;Studio&nbsp;2008 and depends on <code>MSVCR90.DLL</code>.</p>
  
  <p>Is this a bad thing? A really bad thing? Should I be worried? The reason I ask is that the runtime heap allocator is complaining about heap corruption. Could this be related to the mixed runtime versions?</p>