MFC/Other DLL Files

  • Article

|  Overview |  How Do I |  FAQ |  Details |  Sample

You can link your application or DLL with the MFC library either statically or dynamically.

Feature Only in Professional and Enterprise Editions   Static linking to MFC is supported only in Visual C++ Professional and Enterprise Editions. For more information, see .

If you dynamically link your application to the MFC library, you will, at a minimum, need to redistribute MFCx0[U].DLL and MSVCRT.DLL, where x is the version number. MFCx0[U].DLL includes all of the basic framework classes. All MFC DLLs use the shared version of the C run-time library; thus, MSVCRT.DLL is required. If your application uses the MFC database classes, such as CRecordset and CRecordView, you will need to redistribute ODBC and any ODBC drivers that your application uses.

If you redistribute any of these MFC DLLs, be sure you distribute the Retail version rather than the Debug version. Debug versions of the DLLs may not be redistributed. (Debug versions of the MFC DLLs have a trailing "D" in their file names, such as in MFCx0D.DLL).

If you modify MFC in any way, you must rename the modified MFC DLL so it will not conflict with the MFC DLL that might be installed by other MFC applications on your user's system. This is not a recommended procedure. For more information, see .