VC工作区类视图中的信息错误的解决以及VC编译器产生的文件介绍

当VC工作区类视图中的信息错误时，可以将VC自动生成的文件（.CLW，.NCB，.OPT，.APS，.PLG ）删除，再令其从新生成，可能会解决工作区类视图中的错误显示问题。

 .CLW 文件是VC Class Wizard信息文件。存放了Class Wizard的信息。ClassWizard生成的用来存放类信息的文件。classwizard信息文件，ini文件的格式。

.NCB 文件是分析器信息文件，是由系统自动产生的。是“No Compile Browser”的缩写，其中存放了供ClassView、WizardBar和Component Gallery使用的信息，由VC开发环境自动生成。无编译浏览文件。当自动完成功能出问题时可以删除此文件。编译工程后会自动生成。

.OPT 文件是IDE的Option文件。VC开发环境自动生成的用来存放WorkSpace中各种选项的文件。工程关于开发环境的参数文件。如工具条位置信息等。

.APS 文件是资源文件的二进制版本。存放二进制资源的中间文件，VC把当前资源文件转换成二进制格式，并存放在APS文件中，以加快资源装载速度。资源辅助文件。

.PLG：编译信息文件，编译时的error和warning信息文件。

这些文件亦不需要放入基线库。

 

另外， VC文件扩展名及其参考： 

.APS：存放二进制资源的中间文件，VC把当前资源文件转换成二进制格式，并存放在APS文件中，以加快资源装载速度。资源辅助文件。 

.BMP：位图资源文件。

.BSC：浏览信息文件，由浏览信息维护工具（BSCMAKE）从原始浏览信息文件（.SBR）中生成，BSC文件可以用来在源代码编辑窗口中进行快速定位。用于浏览项目信息的，如果用source brower的话就必须有这个文件。可以在project options里去掉Generate Browse Info File，这样可以加快编译进度。

.C：用C语言编写的源代码文件。

.CLW：ClassWizard生成的用来存放类信息的文件。classwizard信息文件，ini文件的格式。 

.CNT：用来定义帮助文件中“Contents”的结构。 

.CPP或.CXX：用C++语言编写的源代码文件。 

.CUR：光标资源文件。 

.DEF：模块定义文件，供生成动态链接库时使用。 

.DLG：定义对话框资源的独立文件。这种文件对于VC工程来说并非必需，因为VC一般把对话框资源放在.RC资源定义文件中。 

.DSP：VC开发环境生成的工程文件，VC4及以前版本使用MAK文件来定义工程。项目文件，文本格式。 

.DSW：VC开发环境生成的WorkSpace文件，用来把多个工程组织到一个WorkSpace中。工作区文件，与.dsp差不多。 

.EXP：由LIB工具从DEF文件生成的输出文件，其中包含了函数和数据项目的输出信息，LINK工具将使用EXP文件来创建动态链接库。只有在编译DLL时才会生成，记录了DLL文件中的一些信息。 

.H、.HPP或.HXX：用C/C++语言编写的头文件，通常用来定义数据类型，声明变量、函数、结构和类。 

.HLP：Windows帮助文件。 

.HM：在Help工程中，该文件定义了帮助文件与对话框、菜单或其它资源之间ID值的对应关系。 

.HPJ：由Help Workshop生成的Help工程文件，用来控制Help文件的生成过程。 

.HPG，生成帮助的文件的工程。 

.ICO：图标资源文件。 

.ILK：连接过程中生成的一种中间文件，只供LINK工具使用。 

.INI：配置文件。 

.LIB：库文件，LINK工具将使用它来连接各种输入库，以便最终生成EXE文件。 

.LIC：用户许可证书文件，使用某些ActiveX控件时需要该文件。 

.MAK：即MAKE文件，VC4及以前版本使用的工程文件，用来指定如何建立一个工程，VC6把MAK文件转换成DSP文件来处理。 

.MAP：由LINK工具生成的一种文本文件，其中包含有被连接的程序的某些信息，例如程序中的组信息和公共符号信息等。执行文件的映像信息记录文件。 

.MDP：旧版本的项目文件，相当于.dsp 

.NCB：NCB是“No Compile Browser”的缩写，其中存放了供ClassView、WizardBar和Component Gallery使用的信息，由VC开发环境自动生成。无编译浏览文件。当自动完成功能出问题时可以删除此文件。编译工程后会自动生成。 

.OBJ：由编译器或汇编工具生成的目标文件，是模块的二进制中间文件。 

.ODL：用对象描述语言编写的源代码文件，VC用它来生成TLB文件。 

.OLB：带有类型库资源的一种特殊的动态链接库，也叫对象库文件。 

.OPT：VC开发环境自动生成的用来存放WorkSpace中各种选项的文件。工程关于开发环境的参数文件。如工具条位置信息等。 

.PBI、.PBO和.PBT：由VC的性能分析工具PROFILE生成并使用的三种文件。 

.PCH：预编译头文件，比较大，由编译器在建立工程时自动生成，其中存放有工程中已经编译的部分代码，在以后建立工程时不再重新编译这些代码，以便加快整个编译过程的速度。

.PDB：程序数据库文件，在建立工程时自动生成，其中存放程序的各种信息，用来加快调试过程的速度。记录了程序有关的一些数据和调试信息。

 .PLG：编译信息文件，编译时的error和warning信息文件。

.RC：资源定义文件。 

.RC2：资源定义文件，供一些特殊情况下使用。 

.REG：注册表信息文件。 

.RES：二进制资源文件，资源编译器编译资源定义文件后即生成RES文件。 

.RTF：Rich Text Format（丰富文本格式）文档，可由Word或写字板来创建，常被用来生成Help文件。 

.SBR：VC编译器为每个OBJ文件生成的原始浏览信息文件，浏览信息维护工具（BSCMAKE）将利用SBR文件来生成BSC文件。 

.TLB：OLE库文件，其中存放了OLE自动化对象的数据类型、模块和接口定义，自动化服务器通过TLB文件就能了解自动化对象的使用方法。

.WAV：声音资源文件。 

另附：

微软支持说明，参考 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 a .CPP or .CXX file or use the /Tp switch when compiling the file. Microsoft recommends that you rename the file to have the .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 a .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 included 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 an .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 an .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 particular segment, and for many 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 the .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 undocumented, 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 (versions 2.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 the .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 the .EXP file when you link a program that both exports to and imports from another program, either directly or indirectly. If you link with an .EXP file, LINK does not produce an import library because it assumes that LIB already created one.

 

.LIB -- Library file: 

These files could 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 includes 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 includes 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 the .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.

 

RCT -- 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.