NET assembly that can be redistributed with an application in its application local folder or by deploying it to the Global Assembly Cache (GAC) by using the Gacutil.exe (Global Assembly Cache Tool).
If your MFC application uses Windows Forms controls, you must redistribute mfcmifc80.dll with your application.
#Thelibrarian mfc drivers
If your application uses the MFC database classes (for example, CRecordset Class and CRecordView Class), you must redistribute ODBC and any ODBC drivers that your application uses.
#Thelibrarian mfc how to
(At a minimum, Internet Explorer 4.0 is required.) Information about how to install Internet Explorer components is available in "Article 185375: How To Create a Single EXE Install of Internet Explorer" on the Microsoft Support website. If your application uses the MFC classes that implement the WebBrowser control (for example, CHtmlView Class or CHtmlEditView Class), we recommend that you also install the most current version of Microsoft Internet Explorer so that the target computer will have the most current common control files. For more information about the recommended strategies for deploying Visual C++ libraries, see Choosing a Deployment Method. However, although static linking may work for testing and internal deployment of applications, we recommend that you do not use it to redistribute MFC. If you statically link your application to MFC (that is, if you specify Use MFC in a Static Library on the General tab in the Property Pages dialog box), you do not have to redistribute an MFC DLL.
You also have to redistribute the matching mfc u.dll or mfc. For example, if your MFC application is built by using the Visual Studio 2013 (vc120) toolset, you must redistribute the msvcr120.dll. If your app is built by using an earlier version of the MFC library, you must redistribute the matching CRT DLL from the redistributable files directory. By default, Visual Studio installs these in C:\Program Files (x86)\Windows Kits\10\Redist\ucrt\DLLs\ in an architecture-specific sub-directory. Redistributable architecture-specific versions of ucrtbase.dll for local deployment are found in the Windows SDK.
#Thelibrarian mfc windows 10
To download the universal CRT for central deployment on supported versions of Windows, see Windows 10 Universal C Runtime. For information on how to redistribute the universal CRT as an operating system component or by using local deployment, see Introducing the Universal CRT. To run an MFC application built by using Visual Studio 2015 on earlier versions of Windows, you must redistribute the Universal CRT. The version of MFC that ships with Visual Studio 2015 uses the universal CRT library, which is distributed as part of Windows 10 and Windows 11. You can use the versions installed by Visual Studio 2015 in the Windows\system32 and Windows\syswow64 directories instead.īecause all MFC DLLs use the shared version of the C runtime library (CRT), You may also need to redistribute the CRT. The mfc140.dll files were omitted from the redistributable files directory in Visual Studio 2015 RTM. For example, if your MFC app is built by using the version of MFC that ships with Visual Studio 2015, you must redistribute mfc140.dll or mfc140u.dll, depending on whether your app is compiled for narrow characters or Unicode support. If you dynamically link your application to the MFC library, you must redistribute the matching MFC DLL.