Re: msvcr71.dll and msvcr80.dll conflict?
"pyramus" <no@none.com> wrote in message
news:qJ-dnRn9X7xMopHb4p2dnA@giganews.com...
Ah, so Microsoft has figured out another method of "encouraging" people to
buy each new compiler they release. Nice work! ;)
Can you define "very limited kind"?
You can have many versions of the CRL loaded, as long as you don't allocate
a resource (memory, file handle,. strtok state, etc) from one copy of the
CRT and expect to use or free it in a different copy of the CRT.
In a nutshell - design your DLL interface so that it's language independent
(C-only, stdcall calling convention, for everything you allocate you provide
a function to release, etc) and you won't have any problems.
The most widely documented, systematic way to accomplish that goal is to
design your DLL as a COM in-process server.
If you pass C++ types across the DLL boundary, you're likely to have
problems, although even that will work under the right circumstances.
Is this also true if one uses the /MT compiler flag? (Of course that then
forces the client to do the same...)
The same issues exist there.
-cd