Shulou(Shulou.com)06/03 Report--

This article will explain in detail how to solve the problem of C runtime error R6034. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

The cause of the C runtime error R6034, an application has tried to load the C runtime library without using a manifest. This way of loading VisualC++DLL is not supported. You need to modify your application to use manifest generation.

Causes and Solutions of C Runtime error R6034

Use the manifest to rebuild the application. Building an application using VisualStudio automatically places the manifest in the generated EXE or DLL file. If you want to build the application on the command line, use the mt.exe tool to add the manifest as a resource. If you want to generate EXE, use the resource ID1;. If you want to generate DLL, use 2. For more information, see how to: embed a manifest into a Cpicket + application.

The solution of causing C Runtime error R6034

According to the corresponding article, modify it as follows to solve this problem successfully (the second step of my modification is to embed Manifest into exe successfully):

1. In the property pages dialog for a project, you can control the generation of manifest files for specific projects. On the configuration Properties tab, click Linker, click manifest file (ManifestFile), and then click generate manifest (GenerateManifest). By default, the project properties of the new project are set to generate manifest files. However, you can also disable the generation of project manifests by using the build manifest property of the project. When this property is set to Yes, a list of the project is generated. Otherwise, when the linker parses dependencies between application code, the assembly information is ignored and no manifest is generated.

The generation system in 2.VisualStudio allows the manifest to be embedded in the final binary application file or generated as an external file. This behavior is controlled by the embed list option in the Project Properties dialog. To set this property, open the inventory tools node and select input and output. If the manifest is not embedded, it will be generated as an external file and saved in the same directory as the final binary file. If you embed the manifest, VisualStudio embeds the final manifest using the following procedure:

(1) after compiling the source code into an object file, the linker collects dependent assembly information. When the final binary is linked, the linker generates an intermediate listing, which will later be used to generate the final listing.

(2) after the intermediate list is generated and the link is completed, the inventory tool is executed to merge into a final list and save it as an external file.

(3) the project generation system then detects whether the information in the manifest generated by the manifest tool is different from that contained in the manifest embedded in the binary file.

This is the end of this article on "how to solve the problem of causing C runtime error R6034". I hope the above content can be helpful to you, so that you can learn more knowledge. If you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.