Every time I write an MFC program it runs fine on my system, since msvc++6 comes with mfc42d.dll. However, when I send the app to other people I have to include a copy of the .dll or they can''t run it. Why is this? I''m pretty sure programs written by other''s don''t require the .dll, otherwise they''d be sending it w/ their apps (and they don''t). Can anyone help me out here? This problem has been bugging me for a while. Thanks in advance. d e e p s k y . s 5 . c o m "If builders made buildings the way programmers write programs, then the first woodpecker to come along would destroy civilization." -Weinberg''s Law

The D in MFC42D.DLL is for a debug release. Standard windows boxes do not ship with debug releases. That''s for development purposes. You need to change your project settings to activate the RELEASE instead of the DEBUG version then compile. Then all should be fine.

YAP-YFIO,
deadlinegrunt

You should compile your program in release mode... the ''d'' in mfc42d.dll stant for Debug.

K with MSVC standard edition when using MFC you get only one option with it, use MFC in a shared dll. Unlike standard windows and other c/c++ programs the libraries arent directly(statically)linked with your application, but instead are loaded on runtime from that dll. If you want to be able to statically link MFC libraries with the your app you'll have to upgrade to the Proffesional version. Only then will you be able to distribute without the dll.
Hope that helped....





Edited by - ghoulflesh on May 6, 2001 3:20:27 AM