Walkthrough: Creating an Inline Task

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 tasks are typically created by compiling a class that implements the ITask interface. Starting with the .NET Framework version 4, you can create tasks inline in the project file. You do not have to create a separate assembly to host the task. For more information, see Inline Tasks.

This walkthrough shows how to create and run these inline tasks:

A task that has no input or output parameters.
A task that has one input parameter and no output parameters.
A task that has two input parameters, and one output parameter that returns an MSBuild property.
A task that has two input parameters, and one output parameter that returns an MSBuild item.

To create and run the tasks, use Visual Studio and the Visual Studio Command Prompt Window, as follows:
Create an MSBuild project file by using Visual Studio.
Modify the project file in Visual Studio to create the inline task.
Use the Command Prompt Window to build the project and examine the results.

Creating and Modifying an MSBuild Project

The Visual Studio project system is based on MSBuild. Therefore, you can create a build project file by using Visual Studio. In this section, you create a Visual C# project file. (You can create a Visual Basic project file instead. In the context of this tutorial, the difference between the two project files is minor.)

To create and modify a project file

In Visual Studio, on the File menu, click 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 InlineTasks. Type a Location for the solution, for example, D:\. Ensure that Create directory for solution is selected, Add to Source Control is cleared, and Solution Name is InlineTasks.

Click OK to create the project file.
In Solution Explorer, right-click the InlineTasks project node, and then click Unload Project.
Right-click the project node again, and then click Edit InlineTasks.csproj.

The project file appears in the code editor.

Adding a Basic Hello Task

Now, add to the project file a basic task that displays the message "Hello, world!" Also add a default TestBuild target to invoke the task.

To add a basic hello task

In the root Project node, change the DefaultTargets attribute to TestBuild.The resulting Project node should resemble this example:

<Project ToolsVersion="4.0" DefaultTargets="TestBuild" xmlns="https://schemas.microsoft.com/developer/msbuild/2003">

Add the following inline task and target to the project file just before the </Project> tag.

<UsingTask TaskName="Hello" TaskFactory="CodeTaskFactory" AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.v4.0.dll" >  
  <ParameterGroup />  
  <Task>  
    <Code Type="Fragment" Language="cs">  
      Log.LogMessage("Hello, world!", MessageImportance.High);  
    </Code>  
  </Task>  
</UsingTask>  
<Target Name="TestBuild">  
  <Hello />  
</Target>

Save the project file.

This code creates an inline task that is named Hello and has no parameters, references, or Using statements. The Hello task contains just one line of code, which displays a hello message on the default logging device, typically the console window.

Running the Hello Task

Run MSBuild by using the Command Prompt Window to construct the Hello task and to process the TestBuild target that invokes it.

To run the Hello task

Click Start, click All Programs, and then locate the Visual Studio Tools folder and click Visual Studio Command Prompt.
In the Command Prompt Window, locate the folder that contains the project file, in this case, D:\InlineTasks\InlineTasks\.
Type msbuild without command switches, and then press ENTER. By default, this builds the InlineTasks.csproj file and processes the default target TestBuild, which invokes the Hello task.
Examine the output in the Command Prompt Window. You should see this line:

Hello, world!

Note

If you do not see the hello message, try saving the project file again and then run the Hello task.

By alternating between the code editor and the Command Prompt Window, you can change the project file and quickly see the results.

Defining the Echo Task

Create an inline task that accepts a string parameter and displays the string on the default logging device.

To define the Echo task

In the code editor, replace the Hello task and TestBuild target by using the following code.

<UsingTask TaskName="Echo" TaskFactory="CodeTaskFactory" AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.v4.0.dll" >  
  <ParameterGroup>  
    <Text Required="true" />  
  </ParameterGroup>  
  <Task>  
    <Code Type="Fragment" Language="cs">  
      Log.LogMessage(Text, MessageImportance.High);  
    </Code>  
  </Task>  
</UsingTask>  
<Target Name="TestBuild">  
  <Echo Text="Greetings!" />  
</Target>

In the Command Prompt Window, type msbuild without command switches, and then press ENTER. By default, this processes the default target TestBuild, which invokes the Echo task.
Examine the output in the Command Prompt Window. You should see this line:

Greetings!

This code defines an inline task that is named Echo and has just one required input parameter Text. By default, parameters are of type System.String. The value of the Text parameter is set when the TestBuild target invokes the Echo task.

Defining the Adder Task

Create an inline task that adds two integer parameters and emits their sum as an MSBuild property.

To define the Adder task

In the code editor, replace the Echo task and TestBuild target by using the following code.

<UsingTask TaskName="Adder" TaskFactory="CodeTaskFactory" AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.v4.0.dll" >  
  <ParameterGroup>  
    <A ParameterType="System.Int32" Required="true" />  
    <B ParameterType="System.Int32" Required="true" />  
    <C ParameterType="System.Int32" Output="true" />  
  </ParameterGroup>  
  <Task>  
    <Code Type="Fragment" Language="cs">  
      C = A + B;  
    </Code>  
  </Task>  
</UsingTask>    
<Target Name="TestBuild">  
  <Adder A="4" B="5">  
    <Output PropertyName="Sum" TaskParameter="C" />  
  </Adder>  
  <Message Text="The sum is $(Sum)" Importance="High" />  
</Target>

In the Command Prompt Window, type msbuild without command switches, and then press ENTER. By default, this processes the default target TestBuild, which invokes the Echo task.
Examine the output in the Command Prompt Window. You should see this line:

The sum is 9

This code defines an inline task that is named Adder and has two required integer input parameters, A and B, and one integer output parameter, C. The Adder task adds the two input parameters and returns the sum in the output parameter. The sum is emitted as the MSBuild property Sum. The values of the input parameters are set when the TestBuild target invokes the Adder task.

Defining the RegX Task

Create an inline task that accepts an item group and a regular expression, and returns a list of all items that have file content that matches the expression.

To define the RegX task

In the code editor, replace the Adder task and TestBuild target by using the following code.

<UsingTask TaskName="RegX" TaskFactory="CodeTaskFactory" AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.v4.0.dll" >  
  <ParameterGroup>  
    <Expression Required="true" />  
    <Files ParameterType="Microsoft.Build.Framework.ITaskItem[]" Required="true" />  
    <Result ParameterType="Microsoft.Build.Framework.ITaskItem[]" Output="true" />  
  </ParameterGroup>  
  <Task>  
    <Using Namespace="System.Text.RegularExpressions"/>  
    <Code Type="Fragment" Language="cs">  
<![CDATA[  
      if (Files.Length > 0)  
      {  
        Result = new TaskItem[Files.Length];  
        for (int i = 0; i < Files.Length; i++)  
        {  
          ITaskItem item = Files[i];  
          string path = item.GetMetadata("FullPath");  
          using(StreamReader rdr = File.OpenText(path))  
          {  
            if (Regex.Match(rdr.ReadToEnd(), Expression).Success)  
            {  
              Result[i] = new TaskItem(item.ItemSpec);  
            }  
          }  
        }  
      }  
]]>  
    </Code>  
  </Task>  
</UsingTask>    
<Target Name="TestBuild">  
  <RegX Expression="public|protected" Files="@(Compile)">  
    <Output ItemName="MatchedFiles" TaskParameter="Result" />  
  </RegX>  
  <Message Text="Input files: @(Compile)" Importance="High" />  
  <Message Text="Matched files: @(MatchedFiles)" Importance="High" />  
</Target>

In the Command Prompt Window, type msbuild without command switches, and then press ENTER. By default, this processes the default target TestBuild, which invokes the RegX task.
Examine the output in the Command Prompt Window. You should see these lines:

Input files: Form1.cs;Form1.Designer.cs;Program.cs;Properties\AssemblyInfo.cs;Properties\Resources.Designer.cs;Properties\Settings.Designer.cs

Matched files: Form1.cs;Form1.Designer.cs;Properties\Settings.Designer.cs

This code defines an inline task that is named RegX and has these three parameters:

Expression is a required string input parameter that has a value that is the regular expression to be matched. In this example, the expression matches the words "public" or "protected".
Files is a required item list input parameter that has a value that is a list of files to be searched for the match. In this example, Files is set to the Compile item, which lists the project source files.
Result is an output parameter that has a value that is the list of files that have contents that match the regular expression.

The value of the input parameters are set when the TestBuild target invokes the RegX task. The RegX task reads every file and returns the list of files that match the regular expression. This list is returned as the Result output parameter, which is emitted as the MSBuild item MatchedFiles.

Handling Reserved Characters

The MSBuild parser processes inline tasks as XML. Characters that have reserved meaning in XML, for example, "<" and ">", are detected and handled as if they were XML, and not .NET source code. To include the reserved characters in code expressions such as Files.Length > 0, write the Code element so that its contents are contained in a CDATA expression, as follows:

<Code Type="Fragment" Language="cs">

<![CDATA[

// Your code goes here.

]]>

</Code>

Share via