First.MFC static library (.lib)
 
 MFC static libraries use the following naming conventions: 
 uAFXcWd.LIB.
 The specifiers for the library naming convention are as follows:
 
 
  
   
   | Specifier 
 | Value and meaning 
 | 
 
   
   |  u  | (n) ANSI or (u) Unicode 
 | 
 
   
   |  c  | Type of plan created: c = all 
 | 
 
   
   |  d  | d = debug version; release specifier omitted 
 | 
 
  
 
 
 The default is to generate a static library for debug versions of windows ANSI applications for Intel platforms: NAFXCWD.Lib.
 All libraries listed in the following table are pre-built static libraries in the \ atlmfc \ lib directory.
 Static link library naming convention:
 
 
  
   
   | Library 
 | Description 
 | 
 
   
   | NAFXCW.LIB 
 | MFC static link library, release version 
 | 
 
   
   | NAFXCWD.LIB 
 | MFC static link library, debug version 
 | 
 
   
   | UAFXCW.LIB 
 | MFC has Unicode static link library support, release version 
 | 
 
   
   | UAFXCWD.LIB 
 | MFC has Unicode static link library support, debug version 
 | 
 
  
 
 
Second.MFC dynamic libraries (including the import library.lib)
 
 The DLLs and libraries included in MFC follow a structured naming convention. This makes it easier to understand which DLL or library should be used for the purpose.
 The import libraries required to build applications or extension DLLs that use these DLLs have the same base name as the DLL, but with a .lib file extension.
 Shared DLL naming convention:
 
 
  
   
   | DLL (import library.lib) 
 | Description 
 | 
 
   
   | MFCxx.DLL (MFCxx.lib / MFCSxx.lib) 
 | MFC DLL, ANSI release 
 | 
 
   
   | MFCxxU.DLL (MFCxxU.lib / MFCSxxU.lib) 
 | MFC DLL, Unicode release version 
 | 
 
   
   | MFCxxD.DLL (MFCxxD.lib / MFCSxxD.lib) 
 | MFC DLL, ANSI debug version 
 | 
 
   
   | MFCxxUD.DLL (MFCxxUD.lib / MFCSxxUD.lib) 
 | MFC DLL, Unicode debug version 
 | 
 
  
 
 
Third. MFC all Unicode library examples
 The Unicode version of the MFC library is as follows:
 Static link library:
 
 
  
   
   | Release 
 | Debug 
 | Instructions 
 | 
 
   
   | UAFXCW.lib, .pdb 
 | UAFXCWD.lib, .pdb 
 | Unicode MFC static link library 
 | 
 
  
 
 
 Dynamic Link Library:
 
 
  
   
   | Release 
 | Debug 
 | Instructions 
 | 
 
   
   | MFC100U.lib, .dbg, def, .dll, .map, .pdb, .prf 
 | MFC100UD.lib, .def, .dll, .map, .pdb 
 | Unicode MFC import library containing code that applications or DLLs must statically link 
 | 
 
   
   | MFCS100U.lib, .pdb 
 | MFCS100UD.lib, .pdb 
 | Unicode MFC import library containing code that applications or DLLs must statically link 
 | 
 
  
 
 
file type:
 
 Import library files have an extension (.lib).
 
 Dynamic link library files have an extension (.dll).
 
 A module definition (.def) file is a text file containing defined .exe or .dll statements.
 
 A map (.map) file is a text file that contains information used by the linker in the linker.
 
 Import library (.lib) files are used with the DLL version of MFC. These files contain code that the application or DLL must statically link.
 
 Debug and project status information in a program database (.pdb) file.
 
 Debug (.dbg) files contain information used by the Visual C ++ debugger (COFF FPO and CodeView).