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

This article is to share with you about the net development process under the Bin directory file format, the editor thinks it is very practical, so share it with you to learn, I hope you can get something after reading this article, say no more, follow the editor to have a look.

In .NET development, we often see these types of files under the bin directory:

.pdb 、 .xsd 、 .vshost.exe 、 .exe 、 .exe.config 、 .vshost.exe.config

When a project is released, it is often unclear what is needed and which is not. So what exactly are these format files for?

Pdb

.pdb file, which is a symbol file (program database) generated by VS for debugging, holds debugging information. In the project properties of VS, Cramp Cleavage formats, debug information format, set / Zi, then VS will create a PDB file when building the project.

Here we need to distinguish between two situations:

1. When building a static library, you can set the name of the generated pdb file in the project properties-> C _ VS2005 +-> output file-> program database name. If not specified, the default is generated as VCx0.pdb, where x is the VS version number, for example, if you use VS2005, you will generate VC80.pdb. This will give rise to a question, when compiling the static library, the default generated .pdb file name is the same, so the project referencing this static library will eventually find the correct .pdb file? The answer is yes, because VS embeds the path of the .pdb file in the generated file.

For example, under Project/ToolA, a static library ToolA.lib is built, corresponding to a vc80.pdb, and also under Project/ ToolB, a static library ToolB.lib is built, corresponding to a vc80.pdb. Then the final project Work.exe links both static libraries at the same time. At this time, when the Work.pdb is generated, the corresponding symbol file path Project/ToolA/vc80.pdb and the symbol file path Project/ToolB/vc80.pdb corresponding to ToolB.lib will be found in ToolA.lib and merged to generate the Work.pdb of the final project.

2. Build an executable file or dynamic library. In this case, the compiler will generate a .pdb file, and the linker will generate a .pdb file. The pdb file generated by the compiler can be set in the project attribute-> Cmax database +-> output file-> program database name. The .pdb file generated by the linker can be set in the project properties-> linker-> debug-> generate debug information (set Yes), and the generator database name is set.

What's the difference between these two pdb files? The pdb file generated by the compiler, which is also named by vcx0 by default, is stored by the compiler in the symbol information corresponding to each .obj file during the compilation process, but does not include the function definition. The .pdb file generated by the linker, which uses the project name by default, is a symbol file with complete information that is further processed by the linker according to the vcx0.pdb generated by the compiler when linking the project. Just as the linker generates exe or dll from each .obj file, the .pdb file generated by the compiler is an intermediate product of the compilation-link process, and finally the ProjectName.pdb generated by the linker is used to debug the program.

The above is the pdb file generation rules. When in use, the debugging period will take the path of the pdb file corresponding to the file, and then go to that path (absolute path) to find it. If the exe or dll is made up by yourself, the debugger will find it no matter where it is placed, as long as the pdb file remains unchanged. If the debugger cannot be found in that path, it will look in the sibling directory of exe or dll. For example, this program is made up by someone else and sent along with the symbol file. We just need to put the symbol file in the same directory as exe or dll, and the debugger can find it. Of course, you can also specify the symbol file path yourself in the debugger

XSD

XSD refers to the XML structure definition (XML Schemas Definition)

XML Schema is a substitute for DTD. The XML Schema language is also called XSD.

XML Schema describes the structure of XML documents. A specified XML Schema can be used to validate an XML document to check that the XML document meets its requirements. Document designers can specify the structure and content allowed by an XML document through XML Schema, and can check whether an XML document is valid or not. XML Schema itself is an XML document that conforms to the XML grammatical structure. It can be parsed with a generic XML parser.

An XML Schema defines the elements that appear in the document, the attributes that appear in the document, the number of child elements, the order of the child elements, whether the element is empty, the data type of the element and attribute, and the default and fixed values of the element or attribute.

The reason why XSD is the replacement of DTD is that it can be extended according to the future conditions, it is richer and more useful than DTD, the third is to write in XML, the fourth is to support data types, and the fifth is to support namespaces.

The suffix of the XSD file is .xsd.

Advantages of XML Schema:

1) XML Schema is based on XML and has no special syntax

2) XML can be parsed and processed like other XML files

3) XML Schema supports a range of data types (int, float, Boolean, date, etc.)

4) XML Schema provides an extensible data model.

5) XML Schema supports integrated namespaces

6) XML Schema supports attribute groups.

.vshost.exe and .exe

.vshost.exe, as the name implies, is the visual studio host application, which is actually opened when vs runs debugging, and this program allows vs to track debugging information. The hosting process is a feature of Visual Studio 2005Accord 2008Universe 201x, which improves debugging performance, supports partial trust debugging, and supports design-time expression evaluation.

The file name of the host process file contains vshost and is located in the output folder of the project. Exe can be opened directly, and vs does not track the operation of any of this file. You can run it directly as long as the referenced assembly is complete.

The difference between .exe.config and .vshost.exe.config

.exe.config is a configuration file that is not debugged.

Vshost.exe.config is a temporary file that is used for debugging generated at debug time.

The contents of the vshost.exe.config file in the folder are exactly the same as .exe.config and are mainly used for host process debugging and should not be run or deployed directly through the application.

These are the file formats under the Bin directory in the net development process, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

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.