Hello,
I have an MFC application built with VC++ 6.0 using mfc42.dll
Windows NT 4 SP 5 comes, AFAIK, just with mfc40.dll, with mfc42.dll being
added to it by VC.
If the application has to be run on an NT machine without Visual, should I
distribute mfc42.dll (almost 1M) along with it (Either statically linked or
as a dll)? I'd rather not do it, since it doubles the size of the result...
So my question is: Is there _any_ way to specify (In build time or later)
that the target is using mfc40.dll, thus saving the extra distribution file?

Thanks In Advance for any tip!

Amir Eliaz

On NT right click the .Exe of your app under windows explorer and check the
dependency of your app. Or you can run depends.exe directly. If you have a
dependency on mfc42.dll you have to ship it. mfc42.dll and mfc40.dll both
are system dlls, so most target windows machines should have it. But they
might not be the latest and greatest ones, so it your app's responsibility
to upgrade it to latest as per your app's requirement. Most likely if you
have written your app using VC6 using MFC, it will have dependency on
mfc42.dll
Here is a good MSDN article about redistributing dlls.
http://www.msdn.microsoft.com/library/techart/redistribvc6.htm or under MSDN
Search Tab, look for "Redistributing Microsoft Visual C++ 6.0 Applications"
with the quotes.
--- VR