On the problem of VC go To definition positioning is not allowed

This is a creation in Article, where the information may have evolved or changed.

Today, a VC project copies a copy to the current folder to save, and the VC opened the copy of the project began to modify the program, found in the use of the header file using go To definition, often jump to the copy of the project source file, rather than the current source file. In addition, remember the previous use of VC also often appear go to definition operation jump is not allowed, always dislocation a few lines. Carefully check the following, found that go to definition and debug/release under the *.bsc file, as long as the deletion of this file, recompile the problem can be solved.

So do, but there is another problem, the following error occurred, can ' t open *.bsc, query reason, because *.BSC is generated at compile time *.sbr build, and my project when compiling a file, there are more than 100 compile errors, the following error:

Fatal error c1003:error count exceeds 100; Stopping compilation

The resulting SBR file generated by compiling the file will not generate the project BSc file.

The workaround allows the project to generate a BSc file by using the method of temporarily not compiling the file, so that the go To definition function is used first. or enlarge the compiler single file maximum compilation error limit, so that it generates SBR file, there is no method found.

Also with VC various extension file function:

Original URL: http://pcedu.pconline.com.cn/empolder/gj/vc/0507/669859.html

. APS: Intermediate files that store binary resources, VC converts the current resource file into binary format and stores it in the APS file to speed up resource loading. resource-assisted files.

. BMP: Bitmap resource file.

. BSC: Browse information files, generated by the Browse Information Maintenance tool (BSCMAKE) from the original browse information file (. SBR), which can be used for quick positioning in the source Code editing window. For browsing project information, you must have this file if you are using source brower. The Generate Browse Info File can be removed from the project options, which speeds up the compilation process.

. C: Source code files written in C language.

. Clw:classwizard the file that is generated to hold the class information. ClassWizard the format of the information file, INI file.

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

. CPP or. CXX: source code files written in the C + + language.

. CUR: Cursor resource file.

. DEF: module definition file for use when generating a dynamic link library.

. DLG: A stand-alone file that defines a dialog box resource. This kind of file is not necessary for VC project, because VC usually put the dialog resources in the. rc resource definition file.

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

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

. Exp: The output file generated by the Lib tool from the Def file, which contains output information for 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 logged.

. H. HPP or. HXX: Header files written in the C + + language, typically used to define data types, declaring variables, functions, structures, and classes.

. Hlp:windows help file.

. HM: In the Help project, the file defines the corresponding relationship between the ID value of the helper file and the dialog box, menu, or other resource.

. HPJ: Help engineering file generated by Help Workshop to control the build process of the Help file.

. HPG, a project that generates help files.

. ICO: Icon resource file.

. ILK: An intermediate file that is generated during the connection process and is intended for use by the link tool only.

. INI: Configuration file.

. LIB: A library file that the link tool uses to connect to various input libraries to eventually generate an EXE file.

. LIC: User License Book file, which is required when using certain ActiveX controls.

. MAK: The Make file, VC4 and previous versions of the project file used to specify how to build a project, VC6 convert MAK files to DSP files for processing.

. MAP: A text file generated by the link tool that contains some information about a connected program, such as group information and public symbolic information in a program. Executes the image information log file for the file.

. MDP: The previous version of the project file, equivalent to. dsp

. NCB:NCB is the abbreviation of "No Compile Browser", which holds information for ClassView, WizardBar and Component Gallery, which is generated automatically by VC development environment. No compiled browse files. You can delete this file when the AutoComplete feature is faulty. It is automatically generated when the project is compiled.

. OBJ: The target file generated by the compiler or assembler tool, which is the binary intermediate file of the module.

. ODL: The source code file written in the object Description language, VC uses it to generate TLB files.

. OLB: A special dynamic-link library with type library resources, also called an object library file.

. OPT:VC a file that is automatically generated by the development environment to hold various options in the workspace. An engineering parameter file for the development environment. such as tool bar location information.

. PBI,. PbO and. PBT: Three types of files generated and used by the VC profiling tool profile.

. PCH: Precompiled header file, relatively large, is generated automatically by the compiler when building the project, which holds some of the code that has been compiled in the project, in the future to build the project will not recompile the code, in order to speed up the entire compilation process.

. PDB: Program database files, which are automatically generated when the project is established, which stores various information about the program to speed up the debugging process. Some data and debugging information about the program are recorded.

. PLG: Compile information files, compile-time error and warning information files.

. RC: Resource definition file.

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

. REG: Registry information file.

. Res: A binary resource file that generates a res file after the Resource compiler compiles the resource definition file.

. The Rtf:rich text format (Rich text formatting) document, which can be created by word or WordPad, is often used to generate help files.

. The SBR:VC compiler generates the original browse information file for each obj file, and the Browse Information Maintenance tool (BSCMAKE) uses the SBR file to generate the BSc file.

. The Tlb:ole library file, which holds the data types, modules, and interface definitions of OLE Automation objects, enables Automation servers to understand how automation objects are used through TLB files.

. WAV: Sound resource file.