Re: msvcr71.dll and msvcr80.dll conflict?

Hi,

I am developing a C++ class library which will be released as a set of
DLLs. I currently build these DLLs under VC7.1 with the Multi-threaded
DLL (/MD) option. I understand that this requires msvcr71.dll and
msvcp71.dll be redistributed in the same directory with my DLLs.

Now, let's say a client running VC8.0 wants to link to my DLLs. Since I
used the /MD option, the client also needs to use the /MD option, and
therefore the application will depend on msvcr80.dll & msvcp80.dll.

If you look at the resulting binary using the depends.exe utility, you
will see that both msvcr71.dll and msvcr80.dll will be loaded. My
question is, is there something inherently wrong with mixing the two
that will cause problems at run-time? I do not anticipate any weird
interactions such as allocating memory in one DLL and deallocating in
another, nor passing file handles across DLL boundaries or anything like
that.

Interested in hearing both the theoretical answer (what Microsoft says
about the issue) and practical experience.