Understanding Visual C + + 6.0 engineering structure

*.dsp

Developer Studio project, project files, text format, but not familiar words do not modify manually.

Note:*.MDP

Microsoft DevStudio Project, an older version of the projects file, prompts you if you want to switch to the new DSP format.

*.dsw

Developer Studio Workspace, is the workspace file, other features similar to DSP. However, it can point to 1 or more *.DSP files.

*.ncb

Waiting to be solved

*.opt

An option file for the IDE (integrated development environment) that works with information about the development environment's parameter files, such as toolbar locations, to save the workspace configuration.

*.plg

Build log file, is compile information file, compile error and warning information file (actually an HTML file), in Tools->options there is an option to control the generation of this file.

*.c

source file

In the Debug folder:

*.pch

pre-compiled file, which is precompiled, can speed up compilation, but the file is very large.

*.pdb

program database, which records some of the data and debugging information, may be useful in debugging.

*.obj

The *.obj file is the target file, which is the binary file generated by the *.c file (source file) after the compilation of the compiled program, which is the *.exe file (executable file) after linking through the linker and the resource file. Obj only gives the relative address of the program, and EXE is the absolute address.

*.idb

Waiting to be solved

*.hpj

Help project, which is the project for generating a helper file, can be handled with microsfot. Compiler.

*.exp

It is generated only when the DLL is compiled, and some information in the DLL file is logged.

*.map

is an image information log file that executes the file, which is generally unnecessary unless you are familiar with the underlying system.

*.mak

This is the project file for the MFC project, which is also a file that is compatible with NMAKE. If you select the external make file option, you can edit it manually, but you cannot take advantage of the many project editing features of Visual C + +.

*.bsc

Browser information file, used to browse information files, if you use source brower, you must have this file. If you don't use this feature, you can remove the Generate Browse Info File from the project options to speed up compilation.

*.aps

Support ResourceView.

*.ncb

Support ClassView.

*.clw

Support ClassWizard.

*. Aps

A binary version of a resource file, a resource-supporting file, is generally not necessary to control him.

*. NCB

No compiled browse file (no compile browser), this file can be deleted when auto-complete function is faulty. Build is generated automatically after the build.

*. CLW

VC Class Wizard information file, stored the Class wizard information. ClassWizard information file, in fact, is the format of INI file, it is interesting to study a bit. Sometimes ClassWizard problems, manual modification CLW file can be solved. If this file does not exist, you will be prompted to rebuild it each time you use ClassWizard.

Understanding Visual C + + 6.0 engineering structure