VC project file description

DSW, APS, CLW, and PLG files can be deleted. Only the read-only attributes of h, C, CPP, DSP, RC, and other files are retained, and all others are deleted. Then, when you enable the DSP, you will be prompted to select YES.

*. DSP (development studio project): It is a VC ++ project configuration file, for example, which file your project contains, what are your compilation options, and so on. DSP configuration.
*. DSW (workflow studio workspace): It is a workspace file used to configure the project file. It can point to one or more. DSP files.
*. CLW: it is a classwizard file. It is actually an INI file format. If you are interested, please study it. sometimes the classwizard has a problem. You can manually modify the CLW file to solve the problem. if this file does not exist, you will be prompted to re-create it each time you use classwizard.
*. Opt: The parameter files of the project about the development environment, such as the tool bar location.
*. APS :( appstudio file): Resource auxiliary file, in binary format. Generally, you do not need to worry about it.
*. RC: resource file. Some resources such as bitmaps and menus are often used in applications. files with the RC extension in VC are called resource files, which contain all the windows resources used in applications, it should be noted that RC files can be edited and modified in a visual manner directly in the VC integration environment.
*. PLG: it is a compilation information file. The error and warning information files during compilation (in fact, it is an HTML file, which is generally of little use ), in tools> options, an option is provided to control the generation of this file.
*. HPJ :( help project) is the project that generates the Help file. It can be processed using microsfot help compiler.
*. MDP: (Microsoft devstudio project) is an earlier version of the project file. To open this file, you will be prompted to convert it to a new DSP format.
*. Bsc: Used to browse project information. This file is required if source Brower is used. If you do not need this function, you can remove the generate browse info file in project options to speed up compilation.
*. Map: The image information record file of the execution file. Unless you are familiar with the underlying system, this file is generally not needed.
*. PCH :( pre-compiled file) is a pre-compiled file, which can speed up compilation, but the file is very large.
*. PDB: (Program database) Records Program-related data and debugging information, which may be useful during debugging.
*. Exp: it is generated only when the DLL is compiled, and some information in the DLL file is recorded. It is generally useless.
*. NCB: no compile browser ). This file can be deleted when the Automatic completion function fails and is automatically generated after build.
*. C: source code file, which is compiled and processed in C language.
*. Cpp: source code file compiled and processed in C ++ syntax.
*. H is the header file, which is generally declared and globally defined.
*. Sln: the solution file used in the development environment. It organizes all elements of one or more projects into a single solution. This file is stored in the parent project directory. solution file, which is a collection of one or more. proj (project files.
*. Vcproj is the project file of VC.

. Vcproj. sln is the project file and solution file above vc2002 respectively.
. DSP. DSW is the project file of vc6 and the project group file respectively.

Convert the vc7 project back to the vc6 project. In other words, the. sln/. vcproj file is converted to the. DSW/. DSP file.

Vc6 enable DSP, DSW, vc2003, 2005, and sln or vcproj

Open the *. DSW file in vc6, and click "! ", And a debug folder in your folder contains the. exe file.

When you open the vc6 project in vc7, it will prompt you whether to convert it to the format of vc7. After conversion, you can use it directly. Vc6 does not know the converted project.

I used vc.net 2003 to open the vc6 project and prompted to upgrade. I also chose yes to all.
However, in fact, vc.net only reads the. DSW and. DSP information of vc6 and Adds. sln and. vcproj.
The DSW and DSP of the vc6 project opened with vc.net have not changed.
Therefore, although the vc6 project opened with vc.net has been "upgraded", DSW and DSP have not been changed.
When I open it again, I don't need DSW, but I use SLN. This is a good job. I just read the information from the project file of vc6 without changing it.
You can use vc6 to open the original DSW and DSP.

------------------------------------------------

Each SLN contains one or more project files. The file extension of the C ++ project file is vcproj.

Vcproj is a standard XML file. Therefore, the following is a description of the node sequence.

The root node is a visual Studio project. Its Attributes contain the global information of the Project. Common Information includes attributes.
Description
Description
 
Projecttype
Engineering type
The default value is Visual C ++.
 
Version
Version
The default value is 7.10.
 
Name
Project name
 
 
Projectguid
Project guid
 
 
Keyword
Engineering keywords
The default value is win32proj.
 
Sccprojectname

Sccauxpath

Scclocalpath

Sccprovider
Sourcesafe Information
The default value is Sak.
 

The subsequent SCC ** attribute marks the project in sourcesafe. When you manually delete a project from sourcesafe, you only need to delete these four attributes. When their default value is Sak, you can find a file mssccprj in the same directory of the project file. SCC, which contains information about the project in sourcesafe. For example, SCC = This is a source code control file.

[PS. vcproj]

Scc_aux_path = "/code-servercode $"

Scc_project_name = "$/project/PS", iqibaaaa
 

It is important to have three subnodes under the root node. Platforms is simple. It indicates the platform content, usually "Win32". mappings are the compilation and link configuration information. Files contains the file information in the project. The following describes operations and files.

Configurations contains configuration information such as project compilation and link. Its Sub-nodes are configuration, which is determined by the compilation type set by the user. By default, there are two sub-nodes: Debug and release. The configuration attributes are as follows:
Description
Description
 
Name
Compilation option name
Usually debug in debug mode | Win32
 
Outputdirectory
Target file output path
The default value is debug.
 
Intermediatedirectory
Compile information output path
The default value is debug.
 
Configurationtype
Engineering type
1 indicates the EXE program file, 2 indicates the DLL dynamic library file, and 3 indicates the Lib static library file.
 
Useofmfc
Indicates whether to use MFC
0 indicates no MFC is used, 1 indicates static link MFC, 2 indicates dynamic link MFC
 
Characterset
Encoding type
1 indicates Unicode, 2 indicates ANSI
 

The sub-nodes of configuration are all tool, and each sub-node has a property name to indicate the meaning of the node. Two subnodes are useful. One is vcclcompilertool, which indicates the compilation information, the other is vclinkertool, which indicates the link information. Other subnodes are not used much.

Common attributes of vcclcompilertool are as follows:
Description
Description
 
Optimization
Optimization Options
Can be 0, 1, 2, 3, 4
 
Preprocessordefinitions
Predefined tag
Usually Win32 _ WINDOWS _ debug
 
Minimalrebuild
Use minimum compilation?
Setting true can save Compilation Time.
 
Basicruntimechecks
Runtime detection, including stack and uninitialized variables
The default value is 3.
 
Runtimelibrary
Running
Select multiple (single) threads, (non) debugging, DLL (exe) Type
 
Treatwchar_tasbuiltintype
Whether to use wchar_t as the built-in type
If it is false, wchar_t is considered to be of the unsigned short type.
 
Forceconformanceinforloopscope
Whether the scope of the variables declared in the IF and for loops is in the loop
7.1 The default value is false, and 8.0 The default value is true.
 
Useprecompiledheader
Predefine header file settings
0 indicates not to use, 1 indicates creating a pre-defined header file, 2 indicates automatic creation, and 3 indicates using a pre-defined header file
 
Precompiledheaderthrough
Predefine header file name
Generally stdafx. h.
 
Precompiledheaderfile
Precompiled information file name
The default value is $ (intdir)/$ (targetname). PCH.
 
WarningLevel
Warning Level
4
 
Detect64bitportabilityproblems
Check whether it is compatible with 64-bit programs
False
 
Debuginformationformat
Debugging information format
It is usually set to 4 in debug and 3 in release.
 

Common attributes of vclinkertool are as follows:
Description
Description
 
Additionaldependencies
Dependent lib File
 
 
Outputfile
Output target file
Default $ (outdir)/folder (projectnamecmd.exe
 
Linkincremental
Incremental compilation
2
 
Additionallibrarydirectories
Location dependent on lib
 
 
Generatedebuginformation
Whether to generate debugging information
Usually true
 
Programdatabasefile
Debugging information file name
$ (Intdir)/$ (projectname). PDB
 
Subsystem
Subsystem
1 is the console, 2 is the windows program
 
Importlibrary
Imported lib File
Default $ (intdir)/$ (projectname). Lib
 

Files contains file information in the project, which consists of filter and file. Filter indicates directory and file indicates file. Each CPP can also contain a sub-node fileconfiguration, which indicates that the content of this CPP file is inconsistent with the global compilation option during compilation, in general, this is not necessary except for the pre-compiled header file. The pre-compiled header must specify its useprecompiledheader information as 1, that is, it creates a pre-defined header file.