This documentation is archived and is not being maintained.

Installation of Localized ATL and MFC Components

Visual Studio .NET 2003


If you use an ActiveX control that depends on MSSTKPRP.dll (typically they will be ATL-based controls) and you want to ship a localized version of the ActiveX control, you can find a localized version of the MSSTKPRP.dll at


Localization using MFC71LOC.dll is deprecated. The simplest and safest approach is to include the localized MFC resources in your application or DLL itself (or its satellite DLL if you are using one). This avoids the problems of installing MFC71LOC.DLL properly. See MFC Technical Note 57 for more information.

If you decide to localize your application's use of the MFC resources by installing an MFC71 localization DLL, follow the instructions in this topic. Like other shared DLLs, an MFC localization DLL should be installed only if its version is newer than the version that is already installed. Therefore, installing this DLL is similar to installing the other DLL(s). See Version Checking of Redistributable Files for more information.

There are several MFC DLLs supplied for various locales. For example, MFC71DEU.dll is the German version and contains version information that identifies it as German locale. If you install any locale DLL, you must ensure the locale for which the DLL is intended matches the locale of the installed Windows system. When you install the DLL, you must rename it to MFC71LOC.dll.

Visual C++ .NET provides two merge modules related to localization:

  • MFC_LOC_E.msm   Contains the localization DLLs for the European versions.
  • MFC_LOC_FE.msm   Contains the localization DLLs for the Asian versions.

When you use one of these merge modules with an appropriate installer that supports merge modules, it will identify and install the appropriate localized version of the DLL in the target system and rename it to MFC71LOC.dll.

You should never install an MFC71LOC.dll on an English system. English resources are built into MFC71.dll, and it is faster to load them from that DLL instead of searching (and loading) an MFC localization DLL first.

For more information on localizing MFC applications, see:

You can find Knowledge Base articles in the MSDN Library or at

See Also

Redistributing a Native C++ Application