VS in the Path macro VC + + in OutDir, ProjectDir, solutiondir various paths turn

Source: Internet
Author: User

Description

$ (RemoteMachine)

Set to the value of the remote computer property on the Debug property page. For more information, see Changing the project settings for A/C + + Debug configuration.

$ (References)

A semicolon-delimited list of references is added to the project.

$ (ConfigurationName)

The name of the current project configuration (for example, "Debug").

$ (PlatformName)

The name of the current project platform (for example, "Win32").

$ (Inherit)

Specifies the order in which inherited properties appear in the command line authored by the project build system. By default, inherited properties appear at the end of the current property.

$ (NoInherit)

Causes any attributes that will be inherited not to be inherited. If you also want to avoid peer-level calculations, use $ (stopevaluating). Using $ (NoInherit) causes any occurrences of $ (Inherit) to be ignored for the same property.

$ (stopevaluating)

Immediately stops the calculation of the macro in the calculation chain. Any value that appears after $ (stopevaluating) will not appear in the calculated value of the macro. If $ (stopevaluating) is before $ (Inherit), the inherited value of the current position in the calculation chain will not be connected to the macro value. $ (stopevaluating) is a feature superset of $ (NoInherit).

$ (ParentName)

The name of the item that contains this project item. The name will be the parent folder name or the project name.

$ (RootNamespace)

Contains the namespace of the application, if any.

$ (IntDir)

The directory path relative to the project directory specified for the intermediate file. it resolves to the value of the "Intermediate Directory" property.

$ (OutDir)

The path of the output file directory, relative to the project directory. This resolves to the value of the output directory property.

$ (DevEnvDir)

The installation directory for Visual Studio. NET (defined as drive + path), including the trailing backslash "\".

$ (InputDir)

Enter the directory of the file (defined as: drive + path), including the trailing backslash "\". If the item is input, this macro is equivalent to $ (projectdir).

$ (InputPath)

The absolute path name of the input file (defined as: Drive + path + base name + file extension). If the item is input, this macro is equivalent to $ (projectpath).

$ (InputName)

Enter a base name for the file. If the item is input, this macro is equivalent to $ (ProjectName).

$ (InputFileName)

The file name of the input file (defined as base name + file extension). If the item is input, this macro is equivalent to $ (projectfilename).

$ (InputExt)

The file name extension of the input file. It includes "." In front of the file name extension. If the item is input, this macro is equivalent to $ (projectext).

$ (ProjectDir)

The Directory of the project (defined as: drive + path), including the trailing backslash "\".

$ (ProjectPath)

The absolute path name of the project (defined as: Drive + path + base name + file extension).

$ (ProjectName)

The base name of the project.

$ (ProjectFileName)

The file name of the project (defined as base name + file extension).

$ (ProjectExt)

The file name extension of the project. It includes "." In front of the file name extension.

$ (SolutionDir)

The Directory of the solution (defined as: drive + path), including the trailing backslash "\".

$ (Solutionpath)

The absolute path name of the solution (defined as: Drive + path + base name + file extension).

$ (SolutionName)

The base name for the solution.

$ (SolutionFileName)

The file name of the solution (defined as base name + file extension).

$ (SolutionExt)

The file name extension of the solution. It includes "." In front of the file name extension.

$ (TargetDir)

The directory of the generated primary output file (defined as: drive + path), including the trailing backslash "\".

$ (TargetPath)

The absolute path name of the generated primary output file (defined as: Drive + path + base name + file extension).

$ (TargetName)

The base name of the generated primary output file.

$ (TargetFileName)

The file name of the generated primary output file (defined as base name + file extension).

$ (Targetext)

The file name extension of the generated primary output file. It includes "." In front of the file name extension.

$ (VSInstallDir)

Install the directory for Visual Studio. NET.

$ (VCInstallDir)

Install the directory for Visual C + +. NET.

$ (FrameworkDir)

Install the directory for the. NET Framework.

$ (frameworkversion)

Version of the. NET Framework used by Visual Studio. Combined with $ (frameworkdir) is the full path to the version of the. NET Framework that Visual Studio uses.

$ (Frameworksdkdir)

The directory where the. NET Framework SDK is installed. The. NET Framework SDK can be installed as part of Visual Studio. NET, or separately.

$ (Webdeploypath)

The relative path from the Web deployment root to the location to which the project output belongs. Returns the same value as RelativePath.

$ (WebDeployRoot)

The absolute path to the <localhost> location. For example, C:\inetpub\wwwroot.

$ (Safeparentname)

The name of the immediate parent of the valid name format. For example, a form is the parent of a. resx file.

$ (Safeinputname)

The name of the file that is the valid class name, but does not include the file extension.

$ (SafeRootNamespace)

The namespace name in which the Project Wizard will add code. This namespace name will only contain characters that are allowed in a valid C + + identifier.

$ (Fxcopdir)

The path to the Fxcop.cmd file. The Fxcop.cmd file is not installed with all Visual C + + versions.

VS in the Path macro VC + + in OutDir, ProjectDir, solutiondir various paths turn

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.