Pre and Post Build event parameters

Question

In Visual Studio, can someone point me to a list of available pre- and post-build events parameters?
eg. $(TargetDir), etc.

Answer 1

This link provides the complete and updated list. However, if it breaks, this answer will be lost.

Currently, for VS 2015, we have:

$(ConfigurationName)
The name of the current project configuration, for example, "Debug|Any CPU".

$(OutDir)
Path to the output file directory, relative to the project directory. This resolves to the value for the Output Directory property. It includes the trailing backslash '\'.

$(DevEnvDir)
The installation directory of Visual Studio 2005 (defined with drive and path); includes the trailing backslash '\'.

$(PlatformName)
The name of the currently targeted platform. For example, "AnyCPU".

$(ProjectDir)
The directory of the project (defined with drive and path); includes the trailing backslash '\'.

$(ProjectPath)
The absolute path name of the project (defined with drive, path, base name, and file extension).

$(ProjectName)
The base name of the project.

$(ProjectFileName)
The file name of the project (defined with base name and file extension).

$(ProjectExt)
The file extension of the project. It includes the '.' before the file extension.

$(SolutionDir)
The directory of the solution (defined with drive and path); includes the trailing backslash '\'.

$(SolutionPath)
The absolute path name of the solution (defined with drive, path, base name, and file extension).

$(SolutionName)
The base name of the solution.

$(SolutionFileName)
The file name of the solution (defined with base name and 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 with drive and path). It includes the trailing backslash '\'.

$(TargetPath)
The absolute path name of the primary output file for the build (defined with drive, path, base name, and 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 and file extension).

$(TargetExt)
The file extension of the primary output file for the build. It includes the '.' before the file extension.

Answer 2

There you go: http://msdn.microsoft.com/en-us/library/42x5kfw4(v=vs.80).aspx

VS 2015 version

Answer 3

Here is a more up to date list of pre and post-build event parameters (common macros for build commands and properties) 2018 link for Visual Studio 2015: https://msdn.microsoft.com/en-us/library/c02as0cs.aspx

$(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. If this is a relative path, intermediate files go to this path appended to the project directory. This path should have a trailing slash. This resolves to the value for the Intermediate Directory property. Do not use $(OutDir) to define this property.

$(OutDir)

Path to the output file directory. If this is a relative path, output files go to this path appended to the project directory. This path should have a trailing slash. This resolves to the value for the Output Directory property. Do not use $(IntDir) to define this property.

$(DevEnvDir)

The installation directory of Visual Studio (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.

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) = v110, $(VSInstallDir) contains the path to the Visual Studio 2012 installation.

$(VCInstallDir)

The directory into which you installed Visual C++.

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) = v140, $(VCInstallDir) contains the path to the Visual C++ 2015 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 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 . 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.