About the list in Visual Studio

The purpose of the list is to specify the DLL and version of the C Runtime Library on which the program depends, including MFC, ATL, and CRT, you can view the release and DEBUG Versions under VC/redist in the Visual Studio installation directory. For details about the dependencies, see the configuration of your project.

 

(One way to determine which Visual C ++ libraries your application depends on is to view the "General" tab in the "Project Settings" dialog box of your project. For example, you may see that the project uses the MFC and ATL libraries. If you select "use MFC in dynamic library", your application will depend on the mfc dll (such as mfc80.dll) at runtime ). If your application does not use MFC or ATL, it may still depend on the CRT Library (if you have selected "multi-thread debugging" for "Runtime Library" on the "Code Generation" tab of "Project Properties" C/C ++ Branch
DLL (/MDD )")

--- This section introduces msdn to understand the dependencies of Visual C ++ applications.

The list can be embedded or not embedded.

The benefits of embedding do not need to pay special attention to putting the list together with the executable program. The defect is that it is not easy to handle problems when a computer runs.

The advantages and disadvantages of not embedding correspond to the one-to-one embedding.

Metadata. manifest.

 

If you adjust the configuration settings from embedded to non-embedded, note that you need to re-compile all dependent external libraries. Otherwise, r6034 may easily occur. An application tries not to use the list to load the C Runtime Library.

 

In addition to the errors caused by the above list, I also encountered the following listing errors: the embedded list program compiled by Visual Studio 2008 SP1 was run on another computer, A configuration error is prompted. When Visual Studio 2008 is used for remote debugging, the error is caused by the list. The process of searching for the error is tortuous. The problem was discovered carefully by the project team lead, the CRT version referenced in the embedded list is inconsistent with the previous CRT library version. vs2008
The version of VC ++ runtime in the manifest file generated by SP1 is 9.0.21022.8, while that of SP1 is 9.0.30729.1. If the problem is found, the problem is solved. You can search for the problem on the Internet. For details, refer to the solution.