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. 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.
0 kommentar(er)
