VS C++ 项目内置变量问题
来源:互联网 发布:佳格大数据怎么样 编辑:程序博客网 时间:2024/05/15 19:55
Macros for Build Commands and Properties
[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
You can use these macros anywhere in a project's Property Pages dialog box where strings are accepted. These macros are not case sensitive.
To display the currently available macros, in the column to the right of a property name, click the drop-down arrow. If Edit is available, click it and then in the edit dialog box, click Macros. For more information, see the Specifying User-Defined Values section of Property Pages (Visual C++).
Macros that are marked "Deprecated" are no longer used or have been replaced by an equivalent item metadata macro (%(name)). Macros that are marked "Deprecated; migrated" are also deprecated. And in addition, if the project that contains the macro is migrated from Visual Studio 2008, Visual Studio converts the macro to the equivalent Visual Studio 2010 macro.
Macro
Description
$(RemoteMachine)
Set to the value of the Remote Machine property on the Debug property page. See Changing Project Settings for a C/C++ Debug Configuration for more information.
$(Configuration)
The name of the current project configuration (for example, "Debug").
$(Platform)
The name of current project platform (for example, "Win32").
$(ParentName)
(Deprecated.) Name of the item containing this project item. This will be the parent folder name, or project name.
$(RootNameSpace)
The namespace, if any, containing the application.
$(IntDir)
Path to the directory specified for intermediate files relative to the project directory. This path should have a trailing slash. This resolves to the value for the Intermediate Directoryproperty.
$(OutDir)
Path to the output file directory, relative to the project directory. This path should have a trailing slash. This resolves to the value for the Output Directory property.
$(DevEnvDir)
The installation directory of Visual Studio 2010 (defined as drive + path); includes the trailing backslash '\'.
$(InputDir)
(Deprecated; migrated.) The directory of the input file (defined as drive + path); includes the trailing backslash '\'. If the project is the input, then this macro is equivalent to $(ProjectDir).
$(InputPath)
(Deprecated; migrated.) The absolute path name of the input file (defined as drive + path + base name + file extension). If the project is the input, then this macro is equivalent to$(ProjectPath).
$(InputName)
(Deprecated; migrated.) The base name of the input file. If the project is the input, then this macro is equivalent to $(ProjectName).
$(InputFileName)
(Deprecated; migrated.) The file name of the input file (defined as base name + file extension). If the project is the input, then this macro is equivalent to $(ProjectFileName).
$(InputExt)
(Deprecated; migrated.) The file extension of the input file. It includes the '.' before the file extension. If the project is the input, then this macro is equivalent to $(ProjectExt).
$(ProjectDir)
The directory of the project (defined as drive + path); includes 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 extension of the project. It includes the '.' before the file extension.
$(SolutionDir)
The directory of the solution (defined as drive + path); includes the trailing backslash '\'.
$(SolutionPath)
The absolute path name of the solution (defined as drive + path + base name + file extension).
$(SolutionName)
The base name of the solution.
$(SolutionFileName)
The file name of the solution (defined as base name + file extension).
$(SolutionExt)
The file extension of the solution. It includes the '.' before the file extension.
$(TargetDir)
The directory of the primary output file for the build (defined as drive + path); includes the trailing backslash '\'.
$(TargetPath)
The absolute path name of the primary output file for the build (defined as drive + path + base name + file extension).
$(TargetName)
The base name of the primary output file for the build.
$(TargetFileName)
The file name of the primary output file for the build (defined as base name + file extension).
$(TargetExt)
The file extension of the primary output file for the build. It includes the '.' before the file extension.
$(VSInstallDir)
The directory into which you installed Visual Studio 2010.
This property contains the version of the targeted Visual Studio, which might be different that the host Visual Studio. For example, when building with $(PlatformToolset) = v90,$(VSInstallDir) contains the path to the Visual Studio 2008 installation.
$(VCInstallDir)
The directory into which you installed Visual C++ 2010.
This property contains the version of the targeted Visual C++, which might be different that the host Visual Studio. For example, when building with $(PlatformToolset) = v90,$(VCInstallDir) contains the path to the Visual C++ 2008 installation.
$(FrameworkDir)
The directory into which the .NET Framework was installed.
$(FrameworkVersion)
The version of the .NET Framework used by Visual Studio. Combined with $(FrameworkDir), the full path to the version of the .NET Framework use by Visual Studio.
$(FrameworkSDKDir)
The directory into which you installed the .NET Framework. The .NET Framework could have been installed as part of Visual Studio 2010 or separately.
$(WebDeployPath)
The relative path from the web deployment root to where the project outputs belong. Returns the same value as RelativePath.
$(WebDeployRoot)
The absolute path to the location of <localhost>. For example, c:\inetpub\wwwroot.
$(SafeParentName)
(Deprecated.) The name of the immediate parent in valid name format. For example, a form is the parent of a .resx file.
$(SafeInputName)
(Deprecated.) The name of the file as a valid class name, minus file extension.
$(SafeRootNamespace)
(Deprecated.) The namespace name in which the project wizards will add code. This namespace name will only contain characters that would be permitted in a valid C++ identifier.
$(FxCopDir)
The path to the fxcop.cmd file. The fxcop.cmd file is not installed with all Visual C++ editions.
- VS C++ 项目内置变量问题
- C#:使用VS内置DataConnectionDialog连接数据库
- [C#] 使用VS内置的数据库连接属性对话框(DataConnectionDialog)
- VS项目之间引用问题
- vs无法引用项目问题
- 解决VS内置IIS Express 连接Oracle失败问题
- c变量声明问题
- maven项目pom文件(1)-内置变量
- [C++]内置类型变量在内存中的存放
- C中的常量后缀表示意义与内置变量范围
- 《C++primer》第二章--变量和基本内置类型
- c++primerP29-----P51 基本内置类型,变量,复合类型
- C++内置类型的成员变量初始值的问题探讨
- VS 2008创建项目(C#)
- [C++]VS跨项目调用全局函数
- vs 空项目无法调试问题...
- VS安装项目生成的快捷方式问题
- VS项目工程环境相关问题
- 二叉树遍历算法
- 优化AutoCAD .NET 程序的加载——Through the Interface
- IOS的开始
- 操作系统--Linux的安装
- Kids Table - Government Shutdown
- VS C++ 项目内置变量问题
- 将ribbon主题应用到对话框中去(转载)
- LINUX 下如何开启 ftp 服务器
- ffmpeg 源码学习 -- 之命令行参数解析
- HDU 3624: Digital Calculator
- 游标
- MFC中连接SQL Server的方法
- Poj 1050 To the Max (最大子矩阵 DP)
- 【Rails】用gem安装MySQL组件出现Failed to build gem native extension错误的解决办法