Troubleshooting of Information errors in the VC workspace Class View and introduction to files generated by the VC Compiler

When the information in the VC workspace Class View is incorrect (. CLW ,. NCB ,. OPT ,. APS ,. PLG) is deleted and re-generated, which may solve the problem of error display in the workspace Class View.

The. CLW file is the VC Class Wizard information file. Stores information about the Class Wizard. Files generated by ClassWizard to store class information. Classwizard information file, INI file format.

The. NCB file is an analyzer information file automatically generated by the system. Is the abbreviation of "No Compile Browser", which stores information for ClassView, WizardBar, and Component Gallery, which is automatically generated by the VC development environment. The Browser file is not compiled. You can delete this file when the Automatic completion function fails. The project is automatically generated after compilation.

The. OPT file is the IDE Option file. Files automatically generated by the VC development environment are used to store various options in the WorkSpace. The parameter file of the project about the development environment. For example, tool bar location information.

The. APS file is the binary version of the resource file. Stores intermediate files of binary resources. VC converts the current resource file to a binary format and stores the files in APS to accelerate resource loading. Resource auxiliary file.

. PLG: compile the information file, the error and warning information files during compilation.

These files do not need to be placed in the baseline library.

 

In addition, the VC file extension and Its Reference:

. APS: An intermediate file for storing binary resources. VC converts the current resource file to a binary format and stores it in the APS file to accelerate resource loading. Resource auxiliary file.

. BMP: a bitmap resource file.

. BSC: a browser information file generated by the browser information maintenance tool (BSCMAKE) from the original browser information file (. SBR). The BSC file can be used to quickly locate the file in the source code editing window. This file is required if source brower is used to browse project information. You can remove Generate Browse Info File from project options to speed up compilation.

. C: source code file written in C language.

. CLW: files generated by ClassWizard to store class information. Classwizard information file, INI file format.

. CNT: used to define the "Contents" structure in the Help file.

. CPP or. CXX: source code file written in C ++.

. CUR: The cursor resource file.

. DEF: module definition file, which can be used to generate a dynamic link library.

. DLG: defines the independent files of the dialog box resources. This file is not required for the VC project, Because VC generally places the dialog box Resources in the. RC resource definition file.

. DSP: The project file generated by the VC development environment. VC4 and earlier versions use the MAK file to define the project. Project file, in text format.

. DSW: WorkSpace file generated by the VC development environment, which is used to organize multiple projects into one WorkSpace. Workspace files, similar to. dsp.

. EXP: the output file generated by the LIB tool from the DEF file, which contains the output information of functions and data items. The LINK tool uses the EXP file to create a dynamic LINK library. It is generated only when the DLL is compiled, and some information in the DLL file is recorded.

. H,. HPP, or. HXX: header files written in C/C ++ are usually used to define data types and declare variables, functions, structures, and classes.

. HLP: Windows Help file.

. HM: In the Help project, this file defines the correspondence between the Help file and the ID value between the dialog box, menu or other resources.

. HPJ: The Help project file generated by Help Workshop, which is used to control the creation process of the Help file.

. HPG, the project that generates the Help file.

. ICO: icon resource file.

. ILK: An intermediate file generated during the connection process. It is only used by the LINK tool.

. INI: configuration file.

. LIB: library file. The LINK tool will use it to connect various input libraries to generate the EXE file.

. LIC: user license file, which is required when using certain ActiveX controls.

. MAK: MAKE file. The project files used in VC4 and earlier versions are used to specify how to create a project. VC6 converts the MAK file into a DSP file for processing.

. MAP: a text file generated by the LINK tool, which contains information about the connected program, such as group information and public symbol information in the program. The image information of the execution file.

. MDP: The old project file, which is equivalent to. dsp

. NCB: NCB is the abbreviation of "No Compile Browser". It stores information used by ClassView, WizardBar, and Component Gallery, which is automatically generated by the VC development environment. The Browser file is not compiled. You can delete this file when the Automatic completion function fails. The project is automatically generated after compilation.

. OBJ: the target file generated by the compiler or assembler. It is the binary intermediate file of the module.

. ODL: source code file written in the Object Description Language. VC uses it to generate a TLB file.

. OLB: A special dynamic link library with type library resources, also known as object library files.

. OPT: files automatically generated by the VC development environment to store various options in the WorkSpace. The parameter file of the project about the development environment. For example, tool bar location information.

. PBI,. PBO, And. PBT: three files generated and used by the VC performance analysis tool PROFILE.

. PCH: Pre-compiled header file, which is large and automatically generated by the compiler when a project is created. It stores some of the Code that has been compiled in the project and will not be re-compiled when the project is created in the future, to speed up the entire compilation process.

. PDB: A program database file that is automatically generated when a project is created. It stores various program information and is used to speed up the debugging process. Records Program-related data and debugging information.

. PLG: compile the information file, the error and warning information files during compilation.

. RC: Resource definition file.

. RC2: Resource definition file for use in special cases.

. REG: Registry information file.

. RES: Binary resource file. After the resource compiler compiles the resource definition file, the RES file is generated.

. RTF: Rich Text Format (Rich Text Format) document, which can be created by Word or WordPad and is often used to generate Help files.

. SBR: The VC compiler generates the original browsing information file for each OBJ file. The browser information maintenance tool (BSCMAKE) will generate the BSC file using the SBR file.

. TLB: OLE library file, which stores the data types, modules, and interface definitions of OLE automation objects. The Automation server can understand how to use automation objects through the TLB file.

. WAV: Audio Resource file.

Appendix:

Microsoft support instructions, reference http://support.microsoft.com/default.aspx? Scid = kb; EN-US; q132340

 

. C -- C language source file:

This file is compiled as a C file. if it contains C ++ code, you must either rename the file to. CPP or. CXX file or use the/Tp switch when compiling the file. microsoft recommends that you rename the file to have. CPP or. CXX extension if the source file contains C ++ code.

 

. CPP or. CXX -- C ++ language source file:

This file is compiled as a C ++ file. to compile it as a C file instead (assuming there is no C ++ code in the source file), you must either rename the file to. C file (recommended) or use the/Tc switch when compiling the file.

 

. H,. HPP, or. HXX -- Header file:

A header file is often used for function prototypes, class definitions, or constant definitions. The. H,. HPP, or. HXX files can be encoded in multiple source files.

 

. INL -- Inline function file:

This file contains inline function definitions.

 

. RC or. RC2 -- Resource file:

This file holds the project's resource information such as the descriptions of a dialog box, a menu bar, or a string table. this file is compiled by the resource compiler (RC. EXE ). when you use Visual C ++'s AppWizard to generate an MFC (Microsoft Foundation Classes) application, you get. RC file for the application. the. RC file can be modified or created by a resource editor, or the App Studio. under some versions of Visual C ++, you will see. RC2 file that also contains resource information.

 

. DEF -- Module definition file:

Depending on your project type, this file may have two purposes. in programs based on Windows and Windows NT, this file may be used to specify a list of exported functions, to control the programs heap size, to specify the attributes of a participant segment, and for each other uses. for an MS-DOS-based MOVE overlay program (16-bit products only), this file is used to specify which segments or which functions are in which overlay.

 

Back to the top

Files Created by Visual C ++

. APS -- Binary version of the resource file:

This is the binary version of the current resource file. App Studio or the resource editor uses it for quick loading.

 

. BSC -- Browser database file:

A single. BSC file is created for each project. to use the Browser, you need to open this file in the Visual C ++ Workbench. it is created from. SBR files when the BSCMAKE tool is run.

 

. CLW -- Class Wizard status file:

This file keeps information about where message-handling functions are kept in your code. the format of this text file is unformatted ented, but it can be regenerated. for more information on how to regenerate this file, please click Contents on the Help menu in App Studio; then click "Using Class Wizard" and "Update Class Wizard when Code Changes."

 

. EXE or. DLL -- Executable or dynamic link library file:

This file is the final linked output file for the project. It contains executable code.

 

. ILK (version2.0 and later only) -- Incremental link information file:

The linker creates this file to allow incremental linking when possible. If you delete it, you will force the linker to perform a full link.

 

. OBJ -- Object module file:

This is the final output file from the compiler. the linker combines these files to create the final. EXE ,. DLL, or. LIB file. the. OBJ files may have different formats in different versions of Visual C ++ or in different vendor's compilers.

 

. PCH -- Precompiled header file:

These files can significantly speed up compile time. They are created when using the/Yc,/Yu, or/YX compiler options.

 

. PDB -- Program database file:

This binary file contains type and symbolic debugging information gathered over the course of compiling and linking the project. the file is for use with the Visual C ++ debugger. object files contain references into. PDB file for debugging information. this design makes object files smaller. see the online reference under the/Zi switch for more information. when you use the/Z7 switch, this file is not created.

 

. SBR -- Source browser file:

This file is created for each source file compiled with either the/FR or/Fr switch. this file contains symbolic information used by the Microsoft Browser Database Maintenance Utility (BSCMAKE) to produce a browser database file (. BSC file ).

 

. WSP -- Workspace information file (16-bit versions only ):

This is a binary file containing information about the state of the WorkBench when it was closed. Such items as source files opened and their window positions are saved in this file.

 

. VCP -- Workspace information file (Visual C ++ 2.x and later only ):

This file is the Visual C ++ version 2.x equivalent of the 16-bit versions '. WSP file.

 

. VCW -- Visual WorkBench Status file (16-bit versions only ):

This file is created on a per-project basis. It works with the. MAK file to fully describe the project to the WorkBench.

 

. EXP -- Export file:

Export files contain information about exported functions and data items. when LIB creates an import library, it also creates an export file. you use. EXP file when you link a program that both exports to and imports from another program, either directly or indirectly. if you link with. EXP file, LINK does not produce an import library because it assumes that LIB already created one.

 

. LIB -- Library file:

These files cocould be standard library or import library files. standard libraries contain objects and are created by the LIB tool. import libraries contain information about exports in other programs and are created either by LINK when it builds a program that contains exports or by the LIB tool.

 

. MAP -- Map file:

A map file is a text file that contains information about the program being linked. the information provided des the module name, the timestamp from the program file header (not from the file system), and a list of groups in the program with each group's starting address, length, group name, and class. it also contains a list of public symbols with each address, symbol name, flat address, and object file where the symbol is defined. A map file also except des the entry point of the program and a list of fixups.

 

. RES -- Compiled resource file:

The. RES file is created by the Resource Compiler (RC ).

 

. HPJ -- Context-sensitive help project file:

This file appears when you use the Visual C ++ AppWizard to create an MFC application that supports context-sensitive help. you need this file to create help files from. RTF files and. BMP files generated by the AppWizard.

 

NCB -- Parser information file:

This file contains information generated by the parser used by the class view and component gallery. If the file is accidentally or deliberately deleted, it is automatically regenerated.

 

MDP -- Microsoft Developer studio Project file:

This file replaces Visual C ++ version 2. x's. VCP file. The. MDP file contains more information about the project than does the. VCP file.

 

RDBMS -- Resource template file:

These files contain information on custom resources that can be used when you insert a resource. It can include menus, toolbars, bitmaps and any of the other resource types listed in the Insert Resource menu.