Walkthrough: Using MSBuild

Article
11/15/2016

Note

This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

MSBuild is the build platform for Microsoft and Visual Studio. This walkthrough introduces you to the building blocks of MSBuild and shows you how to write, manipulate, and debug MSBuild projects. You will learn about:

Creating and manipulating a project file.
How to use build properties
How to use build items.

You can run MSBuild from Visual Studio, or from the Command Window. In this walkthrough, you create an MSBuild project file using Visual Studio. You edit the project file in Visual Studio, and use a Command Window to build the project and examine the results.

Creating an MSBuild Project

The Visual Studio project system is based on MSBuild. This makes it easy to create a new project file using Visual Studio. In this section, you create a Visual C# project file. You can choose to create a Visual Basic project file instead. In the context of this walkthrough, the difference between the two project files is minor.

To create a project file

Open Visual Studio.
On the File menu, point to New, and then click Project.
In the New Project dialog box, select the Visual C# project type, and then select the Windows Forms Application template. In the Name box, type BuildApp. Enter a Location for the solution, for example, D:\. Accept the defaults for Create directory for solution (selected), Add to Source Control (not selected), and Solution Name (BuildApp).

Click OK to create the project file.

Examining the Project File

In the previous section, you used Visual Studio to create a Visual C# project file. The project file is represented in Solution Explorer by the project node named BuildApp. You can use the Visual Studio code editor to examine the project file.

To examine the project file

In Solution Explorer, click the project node BuildApp.
In the Properties browser, notice that the Project File property is BuildApp.csproj. All project files are named with the suffix "proj". If you had created a Visual Basic project, the project file name would be BuildApp.vbproj.
Right-click the project node, then click Unload Project.
Right-click the project node again, then click Edit BuildApp.csproj.

The project file appears in the code editor.

Targets and Tasks

Project files are XML-formatted files with the root node Project.

<?xml version="1.0" encoding="utf-8"?>  
<Project ToolsVersion="12.0" DefaultTargets="Build"  xmlns="https://schemas.microsoft.com/developer/msbuild/2003">

You must specify the xmlns namespace in the Project element.

The work of building an application is done with Target and Task elements.

A task is the smallest unit of work, in other words, the "atom" of a build. Tasks are independent executable components which may have inputs and outputs. There are no tasks currently referenced or defined in the project file. You add tasks to the project file in the sections below. For more information, see the Tasks topic.
A target is a named sequence of tasks. There are two targets at the end of the project file that are currently enclosed in HTML comments: BeforeBuild and AfterBuild.
```
<Target Name="BeforeBuild">  
</Target>  
<Target Name="AfterBuild">  
</Target>  
```
For more information, see the Targets topic.

The Project node has an optional DefaultTargets attribute that selects the default target to build, in this case Build.

<Project ToolsVersion="12.0" DefaultTargets="Build" ...

The Build target is not defined in the project file. Instead, it is imported from the file Microsoft.CSharp.targets by using the Import element.

<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />

Imported files are effectively inserted into the project file wherever they are referenced.

MSBuild keeps track of the targets of a build, and guarantees that each target is built no more than once.

Adding a Target and a Task

Add a target to the project file. Add a task to the target that prints out a message.

To add a target and a task

Add these lines to the project file, just after the Import statement:
```
<Target Name="HelloWorld">  
</Target>  
```
This creates a target named HelloWorld. Notice that you have Intellisense support while editing the project file.

Add lines to the HelloWorld target, so that the resulting section looks like this:

<Target Name="HelloWorld">  
  <Message Text="Hello"></Message>  <Message Text="World"></Message>  
</Target>

Save the project file.

The Message task is one of the many tasks that ships with MSBuild. For a complete list of available tasks and usage information, see Task Reference.

The Message task takes the string value of the Text attribute as input and displays it on the output device. The HelloWorld target executes the Message task twice: first to display "Hello", and then to display "World".

Building the Target

Run MSBuild from the Visual Studio Command Prompt to build the HelloWorld target defined above. Use the /target or /t command line switch to select the target.

Note

We will refer to the Visual Studio Command Prompt as the Command Window in the sections below.

To build the target

Click Start, then click All Programs. Locate and click the Visual Studio Command Prompt in the Visual Studio Tools folder.
From the command window, navigate to the folder containing the project file, in this case, D:\BuildApp\BuildApp.
Run msbuild with the command switch /t:HelloWorld. This selects and builds the HelloWorld target:
```
msbuild buildapp.csproj /t:HelloWorld  
```
Examine the output in the Command window. You should see the two lines "Hello" and "World":
```
Hello  
World  
```

Note

If instead you see The target "HelloWorld" does not exist in the project then you probably forgot to save the project file in the code editor. Save the file and try again.

By alternating between the code editor and the command window, you can change the project file and quickly see the results.

Note

If you run msbuild without the /t command switch, msbuild builds the target given by the DefaultTarget attribute of the Project element, in this case "Build". This builds the Windows Forms application BuildApp.exe.

Build Properties

Build properties are name-value pairs that guide the build. Several build properties are already defined at the top of the project file:

<PropertyGroup>  
...  
  <ProductVersion>10.0.11107</ProductVersion>  
  <SchemaVersion>2.0</SchemaVersion>  
  <ProjectGuid>{30E3C9D5-FD86-4691-A331-80EA5BA7E571}</ProjectGuid>  
  <OutputType>WinExe</OutputType>  
...  
</PropertyGroup>

All properties are child elements of PropertyGroup elements. The name of the property is the name of the child element, and the value of the property is the text element of the child element. For example,

<TargetFrameworkVersion>v12.0</TargetFrameworkVersion>

defines the property named TargetFrameworkVersion, giving it the string value "v12.0".

Build properties may be redefined at any time. If

<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>

appears later in the project file, or in a file imported later in the project file, then TargetFrameworkVersion takes the new value "v3.5".

Examining a Property Value

To get the value of a property, use the following syntax, where PropertyName is the name of the property:

$(PropertyName)

Use this syntax to examine some of the properties in the project file.

To examine a property value

From the code editor, replace the HelloWorld target with this code:

<Target Name="HelloWorld">  
  <Message Text="Configuration is $(Configuration)" />  
  <Message Text="MSBuildToolsPath is $(MSBuildToolsPath)" />  
</Target>

Save the project file.
From the Command Window, enter and execute this line:
```
msbuild buildapp.csproj /t:HelloWorld  
```
Examine the output. You should see these two lines (your .NET Framework version may differ):
```
Configuration is Debug  
MSBuildToolsPath is C:\Program Files\MSBuild\12.0\bin  
```

Note

If you don't see these lines then you probably forgot to save the project file in the code editor. Save the file and try again.

Conditional Properties

Many properties like Configuration are defined conditionally, that is, the Condition attribute appears in the property element. Conditional properties are defined or redefined only if the condition evaluates to "true". Note that undefined properties are given the default value of an empty string. For example,

<Configuration   Condition=" '$(Configuration)' == '' ">Debug</Configuration>

means "If the Configuration property has not been defined yet, define it and give it the value 'Debug'".

Almost all MSBuild elements can have a Condition attribute. For more discussion about using the Condition attribute, see Conditions.

Reserved Properties

MSBuild reserves some property names to store information about the project file and the MSBuild binaries. MSBuildToolsPath is an example of a reserved property. Reserved properties are referenced with the $ notation like any other property. For more information, see How to: Reference the Name or Location of the Project File and MSBuild Reserved and Well-Known Properties.

Environment Variables

You can reference environment variables in project files the same way as build properties. For example, to use the PATH environment variable in your project file, use $(Path). If the project contains a property definition that has the same name as an environment variable, the property in the project overrides the value of the environment variable. For more information, see How to: Use Environment Variables in a Build.

Setting Properties from the Command Line

Properties may be defined on the command line using the /property or /p command line switch. Property values received from the command line override property values set in the project file and environment variables.

To set a property value from the command line

From the Command Window, enter and execute this line:

msbuild buildapp.csproj /t:HelloWorld /p:Configuration=Release

Examine the output. You should see this line:
```
Configuration is Release.  
```
MSBuild creates the Configuration property and gives it the value "Release".

Special Characters

Certain characters have special meaning in MSBuild project files. Examples of these characters include semicolons (;) and asterisks (*). In order to use these special characters as literals in a project file, they must be specified by using the syntax %xx, where xx represents the ASCII hexadecimal value of the character.

Change the Message task to show the value of the Configuration property with special characters to make it more readable.

To use special characters in the Message task

From the code editor, replace both Message tasks with this line:

<Message Text="%24(Configuration) is %22$(Configuration)%22" />

Save the project file.
From the Command Window, enter and execute this line:
```
msbuild buildapp.csproj /t:HelloWorld  
```
Examine the output. You should see this line:
```
$(Configuration) is "Debug"  
```
For more information, see MSBuild Special Characters.

Build Items

An item is a piece of information, typically a file name, that is used as an input to the build system. For example, a collection of items representing source files might be passed to a task named Compile to compile them into an assembly.

All items are child elements of ItemGroup elements. The item name is the name of the child element, and the item value is the value of the Include attribute of the child element. The values of items with the same name are collected into item types of that name. For example,

<ItemGroup>  
    <Compile Include="Program.cs" />  
    <Compile Include="Properties\AssemblyInfo.cs" />  
</ItemGroup>

defines an item group containing two items. The item type Compile has two values: "Program.cs" and "Properties\AssemblyInfo.cs".

The following code creates the same item type by declaring both files in one Include attribute, separated by a semicolon.

<ItemGroup>  
    <Compile Include="Program.cs;Properties\AssemblyInfo.cs" />  
</ItemGroup>

For more information, see Items.

Note

File paths are relative to the folder containing the MSBuild project file.

Examining Item Type Values

To get the values of an item type, use the following syntax, where ItemType is the name of the item type:

@(ItemType)

Use this syntax to examine the Compile item type in the project file.

To examine item type values

From the code editor, replace the HelloWorld target task with this code:

<Target Name="HelloWorld">  
  <Message Text="Compile item type contains @(Compile)" />  
</Target>

Save the project file.
From the Command Window, enter and execute this line:
```
msbuild buildapp.csproj /t:HelloWorld  
```
Examine the output. You should see this long line:
```
Compile item type contains Form1.cs;Form1.Designer.cs;Program.cs;Properties\AssemblyInfo.cs;Properties\Resources.Designer.cs;Properties\Settings.Designer.cs  
```
The values of an item type are separated with semicolons by default.

To change the separator of an item type, use the following syntax, where ItemType is the item type and Separator is a string of one or more separating characters:

@(ItemType, Separator)

Change the Message task to use carriage returns and line feeds (%0A%0D) to display Compile items one per line.

To display item type values one per line

From the code editor, replace the Message task with this line:

<Message Text="Compile item type contains @(Compile, '%0A%0D')" />

Save the project file.
From the Command Window, enter and execute this line:

msbuild buildapp.csproj /t:HelloWorld

Examine the output. You should see these lines:

Compile item type contains Form1.cs  
Form1.Designer.cs  
Program.cs  
Properties\AssemblyInfo.cs  
Properties\Resources.Designer.cs  
Properties\Settings.Designer.cs

Include, Exclude, and Wildcards

You can use the wildcards "*", "**", and "?" with the Include attribute to add items to an item type. For example,

<Photos Include="images\*.jpeg" />

adds all files with the file extension ".jpeg" in the images folder to the Photos item type, while

<Photos Include="images\**.jpeg" />

adds all files with the file extension ".jpeg" in the images folder, and all its subfolders, to the Photos item type. For more examples, see How to: Select the Files to Build.

Notice that as items are declared they are added to the item type. For example,

<Photos Include="images\*.jpeg" />  
<Photos Include="images\*.gif" />

creates an item type named Photo containing all files in the image folder with a file extension of either ".jpeg" or ".gif". This is equivalent to the following line:

<Photos Include="images\*.jpeg;images\*.gif" />

You can exclude an item from an item type with the Exclude attribute. For example,

<Compile Include="*.cs" Exclude="*Designer*">

adds all files with the file extension".cs" to the Compile item type, except for files whose names contain the string "Designer". For more examples, see How to: Exclude Files from the Build.

The Exclude attribute only affects the items added by the Include attribute in the item element that contains them both. For example,

<Compile Include="*.cs" />  
<Compile Include="*.res" Exclude="Form1.cs">

would not exclude the file Form1.cs, which was added in the preceding item element.

To include and exclude items

From the code editor, replace the Message task with this line:
```
<Message Text="Compile item type contains @(XFiles)" />  
```

Add this item group just after the Import element:

<ItemGroup>  
   <XFiles Include="*.cs;properties/*.resx" Exclude="*Designer*" />  
</ItemGroup>

Save the project file.
From the Command Window, enter and execute this line:
```
msbuild buildapp.csproj /t:HelloWorld  
```

Examine the output. You should see this line:

Compile item type contains Form1.cs;Program.cs;Properties/Resources.resx

Item Metadata

Items may contain metadata in addition to the information gathered from the Include and Exclude attributes. This metadata can be used by tasks that require more information about items than just the item value.

Item metadata is declared in the project file by creating an element with the name of the metadata as a child element of the item. An item can have zero or more metadata values. For example, the following CSFile item has Culture metadata with a value of "Fr":

<ItemGroup>  
    <CSFile Include="main.cs">  
        <Culture>Fr</Culture>  
    </CSFile>  
</ItemGroup>

To get the metadata value of an item type, use the following syntax, where ItemType is the name of the item type and MetaDataName is the name of the metadata:

%(ItemType.MetaDataName)

To examine item metadata

From the code editor, replace the Message task with this line:

<Message Text="Compile.DependentUpon: %(Compile.DependentUpon)" />

Save the project file.
From the Command Window, enter and execute this line:
```
msbuild buildapp.csproj /t:HelloWorld  
```
Examine the output. You should see these lines:
```
Compile.DependentUpon:  
Compile.DependentUpon: Form1.cs  
Compile.DependentUpon: Resources.resx  
Compile.DependentUpon: Settings.settings  
```
Notice how the phrase "Compile.DependentUpon" appears several times. The use of metadata with this syntax within a target causes "batching". Batching means that the tasks within the target are executed once for each unique metadata value. This is the MSBuild script equivalent of the common "for loop" programming construct. For more information, see Batching.

Well-Known Metadata

Whenever an item is added to an item list, that item is assigned some well-known metadata. For example, %(Filename) returns the file name of any item. For a complete list of well-known metadata, see Well-known Item Metadata.

To examine well-known metadata

From the code editor, replace the Message task with this line:

<Message Text="Compile Filename: %(Compile.Filename)" />

Save the project file.
From the Command Window, enter and execute this line:
```
msbuild buildapp.csproj /t:HelloWorld  
```
Examine the output. You should see these lines:
```
Compile Filename: Form1  
Compile Filename: Form1.Designer  
Compile Filename: Program  
Compile Filename: AssemblyInfo  
Compile Filename: Resources.Designer  
Compile Filename: Settings.Designer  
```
By comparing the two examples above, you can see that while not every item in the Compile item type has DependentUpon metadata, all items have the well-known Filename metadata.

Metadata Transformations

Item lists can be transformed into new item lists. To transform an item list, use the following syntax, where ItemType is the name of the item type and MetadataName is the name of the metadata:

@(ItemType -> '%(MetadataName)')

For example, an item list of source files can be transformed into a collection of object files using an expression like @(SourceFiles -> '%(Filename).obj'). For more information, see Transforms.

To transform items using metadata

From the code editor, replace the Message task with this line:

<Message Text="Backup files: @(Compile->'%(filename).bak')" />

Save the project file.
From the Command Window, enter and execute this line:
```
msbuild buildapp.csproj /t:HelloWorld  
```

Examine the output. You should see this line:

Backup files: Form1.bak;Form1.Designer.bak;Program.bak;AssemblyInfo.bak;Resources.Designer.bak;Settings.Designer.bak

Notice that metadata expressed in this syntax does not cause batching.

What's Next?

To learn how to create a simple project file one step at a time, try out the Walkthrough: Creating an MSBuild Project File from Scratch.

Partager via

Walkthrough: Using MSBuild

Creating an MSBuild Project

To create a project file

Examining the Project File

To examine the project file

Targets and Tasks

Adding a Target and a Task

To add a target and a task

Building the Target

To build the target

Build Properties

Examining a Property Value

To examine a property value

Conditional Properties

Reserved Properties

Environment Variables

Setting Properties from the Command Line

To set a property value from the command line

Special Characters

To use special characters in the Message task

Build Items

Examining Item Type Values

To examine item type values

To display item type values one per line

Include, Exclude, and Wildcards

To include and exclude items

Item Metadata

To examine item metadata

Well-Known Metadata

To examine well-known metadata

Metadata Transformations

To transform items using metadata

What's Next?

See Also

Ressources supplémentaires