Files used by Visual C + +

. C-c Language source files:

This file is compiled into a C file. If it contains C + + code, you must rename the file to. CPP or. CXX files, or use the/TP switch when compiling files. If the source file contains C + + code, Microsoft recommends renaming the file to have. CPP or. CXX extension.

. CPP or. Cxx-c++ Language source files:

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

. H. HPP or. HXX-header file:

Header files are often used for function prototypes, class definitions, or constant definitions. H. HPP or. The HXX file can be included in multiple source files.

. INL-inline function file:

This file contains inline function definitions.

. RC or. RC2-Resource file:

This file contains resource information for the project, such as a description of a dialog box, menu bar, or string table. This file is created by the resource compiler (RC. EXE) compiled. When you build an MFC (Microsoft Foundation Class) application using Visual C + + AppWizard, you get the application. RC file: RC files can be modified or created using the Resource editor or App Studio. In some versions of Visual C + +, you will see. The RC2 file also contains resource information.

. DEF-module definition file:

Depending on the project type, this file has two uses. In Windows and Windows NT-based programs, this file is used to specify the list of functions exported, control the heap size, specify attributes for special segments, and so on. For MS-DOS-based MOVE overlay programs (only for 16-bit products), this file is used to specify the overwriting program where the segment or function resides.

Files created by Visual C + +

. APS-binary form of resource files:

This type of file is the current resource file in binary form. APP Studio or the resource Editor uses the file for fast loading.

. BSC-Browser Database file:

Create one for each project. BSC file. To use the browser, you need to open the file in Visual C + + Workbench. This file is passed when you run the BSCMAKE tool. SBR file is created.

. CLW-Class Wizard state file:

This file holds information about where the message-handler functions are stored in the code. The format of this text file is not recorded, but it can be regenerated. For more information about how to regenerate this file, in App Studio, click Content on the Help menu, and then click the Use Class Wizard and Update Class wizard when code changes.

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

This file is the final link output file for the project, which contains executable code.

. ILK (for version 2.0 and later only)-Incremental link information file:

The linker creates this kind of file to allow incremental links to be performed when possible. If you delete this file, the linker is forced to perform a full link.

. OBJ-Object Module file:

This is the final output file of the compiler. The linker will combine these files to create the final. Exe. DLL or. LIB file. In different versions of Visual C + + or in the compilers of different vendors. The OBJ file may have a different format.

. PCH-Precompiled Header file:

These files can greatly improve the speed of compilation. If you use the/yc,/yu, or/yx compiler option, these files are created.

. PDB-Program Database file:

This binary file contains debugging information about the types and symbols that are collected during the compilation and linking of the project. This file is used for the Visual C + + debugger. The object file contains the pair. A reference to the debug information in the PDB file. This design reduces the size of the object file. For more information, see the online reference under the/zi switch. This file is not created when you use the/z7 switch.

. SBR-Source Browser file:

Each source file that is compiled with the/FR or/FR switch will create such a file. This file contains the Microsoft Browser Database Maintenance Utility (BSCMAKE) Build Browser database file (. BSC file) is used for symbolic information.

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

This binary file contains state information when the WorkBench is closed. Items such as open source files and their window locations are saved in this file.

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

This file is associated with the 16-bit version. The WSP file is equivalent to the Visual C + + 2.x version file.

. Vcw-visual WorkBench Status file (only for 16-bit editions):

This file is created on a per-project basis. it with. MAK files to describe the project to Workbench in a comprehensive manner.

. EXP-Export File:

The export file contains information about the exported functions and data items. When LIB creates an import library, it creates an export file at the same time. When you link a program that is exported to another program and imported from another program, it is used directly or indirectly. EXP file. If you use. EXP file is linked, link does not generate an import library because it believes that LIB has created an import library.

. LIB-Library file:

These files can be either standard libraries or import library files. The standard library contains objects, which are created by the LIB tool. The import library contains export information from other programs, either created by LINK when the program that contains the exported information is generated, or created by the LIB tool.

. Map-Map File:

A mapping file is a text file that contains information about a linked program. The included information includes the module name, the timestamp from the program header file (not the file system), and a list of groups in the program that contain the start address, length, group name, and class for each group. Also included is a list of public symbols with the address, symbol name, flat address, and object file defining the symbol for each symbol. The mapping file also includes the entry point and remediation list for the program.

. RES-Compiled resource file:

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

. HPJ-context-sensitive Help project file:

This file is generated when you use Visual C + + AppWizard to create an MFC application that supports context-sensitive help. This file needs to be generated using AppWizard. RTF files and. BMP file to create a Help file.

NCB-Parser information file:

This file contains information generated by the parser used by the Class View and component library. If the file is intentionally or unintentionally deleted, it will be regenerated automatically.

Mdp-microsoft Developer Studio Project files:

This file replaces the Visual C + + version 2.x. VCP file. And. VCP files compared to the. MDP files contain more project information.

RCT-Resource Template file:

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

Other files that were created and then deleted during the build process

During the build process, the Visual C + + IDE also creates two additional files. They should be removed under normal circumstances. These files are:

. CRF-linker response file:

The file is created at any time during the build process.

MSVC. BND-Project. Copy of CRF file:

The file is created when the resource needs to be bound to an executable file. It's just a project. A copy of the CRF file. Some additional files are also created, depending on the features supported by the project. For example, your project might have one or more bands. ICO extension icon file, band. CUR extension of the cursor file or band. BMP extension of the bitmap file. The project may also contain project registry information. REG file. Projects that support OLE may also have. ODL file and. TLB file.

When you check in a file, Visual C + + automatically prompts you to check in the Project Workspace pane plus all the files in the project build file (. mak). In most cases these are just the source files that will need to be opened and rebuilt for Visual C + + projects.

You can add a binary file to a Visual C + + project. They will appear in the Project Workspace pane, and Visual C + + will attempt to add them to source control. 鍦 Do you FAI bang tears cases kernel code lower this is ideal (for instance bitmaps) and in other cases it is not worth (for instance import libraries).

The following is a list of (non-exhaustive) file name extension files that should be added to source control, under normal circumstances:

   . Mak,. DSP,. C,. RC,. RC2,. ico,. bmp,. txt,. def,. hpj,. bat,. rtf,. odl,. inf,.. Reg,. cnt,. cpp,.   cxx,. h,. HPP,. HX X,. INL,. TPL,. VTP, and   . mst.

Again normally, these files cannot be easily generated. There is no need to share source control issues to consider when generating files. These issues are discussed in the Visual C + + online documentation. See the reference section below.

The following is a list of (non-exhaustive) file name extension files that should not be added to source control, under normal circumstances:

    . pch,. MDP,. NCB,. CLW,. obj,. exe,. APS,. cpl,. awk,. Exp,. LIB,. IDB,.   opt,. pdb,. Map,. Res,. Ilk,. SCC,. BSC,. SBR ,. dll, and. tlb.

Typically, these files are automatically regenerated by Visual C + + in open, edit, and build projects.