Printable View
Are the MFC and CRT DLLs shipped with VC 6.0 backwardly compatible with VC 4.2. DLLs? I have noticed that apps that were
built with VC 4.2, do not execute (DLLs fail to load, or oridinals not found) when the DLLs from VC 6.0 have replaced those from
VC 4.2 in the SYSTEM directory. Any ideas?
Yes, Microsoft needs a better way of distributing and naming their DLL's. That's why I always build my MFC applications with the static MFC libraries. This way, when VC++ 7.0 comes out, my application built with VC++ 4.2 will still run, regardless of what changes are made in the MFC DLL's.
Regards,
Paul McKenzie
I can only confirm these problems. So unless you don't go for statically linked libs there is probably no other way around as to copy MFC dll's into private app directory.