Re: VS2005 linking to msvcrt.lib
There shouldn't be a problem of both runtimes being loaded
in the same process by different DLLs. The problem of different
CRT version comes with linking static libs compiled with different
compilers, but shouldn't be an issue for DLLs (provided your
DLLs only export C functions, not C++ classes, and beware
function arguments - don't pass C++ classes or they will get
exported as well; passing C++ interfaces is fine though since
these are essentially pure vtables with no regular methods nor
members to export - that's how COM works for example).
You still need to be careful to let each DLL manage its own
objects, otherwise memory errors will occur (one CRT cannot
deallocate memory allocated by another CRT).
Also, consider static CRT linking.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"venkat" <venkat9200@gmail.com> wrote in message
news:1187690932.823186.107720@r29g2000hsg.googlegroups.com...
Hi
i'm having a problem of my dll linking to msvcr80.dll.This dll was
built with VS2005.
Legacy code(built with vc 6.0) inside my project is not accepting this
dll.
what should i do to link my vc++ projects in VS2005 to link to
msvcrt.dll?
Some of my VS2005 dll's also use MFC80u.dll in this case what should i
do?
Thanks in advance.
regards
venkat