About Macros in system attributes of Visual Studio

Source: Internet
Author: User

Automatically package event attributes generated by projects

 

Http://www.cnblogs.com/nuoyafanfzhou/

 

Macro

Description

$ (Configurationname)

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

$ (Intdir)

Specifies the directory path relative to the project directory for the intermediate file. It is parsed as the value of the "Intermediate directory" attribute.

$ (Outdir)

Path of the output file directory, relative to the project directory. This is resolved to the value of the "output directory" attribute.

$ (Devenvdir)

Visual Studio. NETInstallation Directory (definition form: Drive + path); including the Backslash "/" at the end

$ (Inputdir)

Directory of the input file (definition: Drive + path); including the Backslash "/" at the end. If the project is input, this macro is equivalent to $ (projectdir ).

$ (Inputpath)

The absolute path name of the input file (definition form: Drive + path + basic name + file extension ). If the project is input, this macro is equivalent to $ (projectpath ).

$ (Inputname)

Enter the basic name of the file. If the project is input, this macro is equivalent to $ (projectname ).

$ (Inputfilename)

Name of the input file (defined as the basic name + file extension ). If the project is input, this macro is equivalent to $ (projectfilename ).

$ (Inputext)

The file extension of the input file. It includes "." Before the file extension. If the project is input, this macro is equivalent to $ (projectext ).

$ (Projectdir)

Project directory (definition form: Drive + path); including the Backslash "/" at the end.

$ (Projectpath)

The absolute path name of the project (definition form: Drive + path + basic name + file extension ).

$ (Projectname)

The basic name of the project.

$ (Projectfilename)

Project File Name (defined as basic name + file extension ).

$ (Projectext)

The file extension of the project. It includes "." Before the file extension.

$ (Solutiondir)

Solution directory (defined in the form of drive + path); including the Backslash "/" at the end.

$ (Solutionpath)

The absolute path name of the solution (definition form: Drive + path + basic name + file extension ).

$ (Solutionname)

The basic name of the solution.

$ (Solutionfilename)

Solution file name (defined as basic name + file extension ).

$ (Solutionext)

The file extension of the solution. It includes "." Before the file extension.

$ (Targetdir)

Directory of the generated primary output file (defined in the form of drive + path), including the Backslash "/" at the end.

$ (Targetpath)

The absolute path name of the generated primary output file (defined in the form of drive + path + basic name + file extension ).

$ (Targetname)

The basic name of the generated primary output file.

$ (Targetfilename)

Name of the generated primary output file (defined as the basic name + file extension ).

$ (Targetext)

The file extension of the generated primary output file. It includes "." Before the file extension.

$ (Vsinstalldir)

Install the Visual Studio. NET directory.

$ (Vcinstalldir)

Install the Visual C ++. Net directory.

$ (Frameworkdir)

Directory for installing. NET Framework.

$ (Frameworkversion)

Visual StudioThe. NET Framework version used. Combined with $ (frameworkdir), it is the complete path of the. NET Framework Version Used by Visual Studio.

$ (Frameworksdkdir)

Install the. NET Framework SDK directory .. . NET Framework SDK can be installed as part of Visual Studio. NET or separately.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

The example in the following table demonstrates how to evaluate Macros in various contexts. When,

When the file is in C:/myidls/stuff. IDL

The project is located in C:/soln/proj. vcproj

Solution in C:/soln. sln

When the platform is Win32

When the intermediate directory is debugint

When the output directory is C:/myoutputs

During configuration debugging

When the output name is game.exe

 

 

Http://blog.csdn.net/li_007/article/details/4161259

Related Article

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.