Skip to content
Switch branches/tags

Latest commit

We were only logging the arguments for messages, but not for errors or warnings. Fortunately we can fix this and avoid incrementing the binlog format version.

First this moves the logic to set the Arguments flag into a common codepath close to Message, and only sets the flag when the arguments are present and we're either a message, warning or error. Previously it was only set for messages (and all types derived from Message).

Technically all BuildStatusEventArgs and CustomBuildEventArgs also inherit from LazyFormattedBuildEventArgs, but the serialization for them is fully manual and we don't even write the message for them at all. We ensure that if by any accident an instance of BuildStatus or some other random type such as CustomBuildEventArgs sets the Arguments, we don't set the flag because we're not going to be writing arguments for those.

We extract a method to log the arguments, and call it for errors and warnings.

Note that this doesn't change the BuildEventArgsReader at all, which proves that a file format version change is not necessary.

This also ensures that the tests for error, warning and message hit both codepaths, with and without arguments.

Fixes #6790.

Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Microsoft.Build (MSBuild)

The Microsoft Build Engine is a platform for building applications. This engine, also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software. Visual Studio uses MSBuild, but MSBuild can run without Visual Studio. By invoking msbuild.exe on your project or solution file, you can orchestrate and build products in environments where Visual Studio isn't installed.

For more information on MSBuild, see the MSBuild documentation on

The changelog has detailed information about changes made in different releases.

Build Status

The current development branch is main. Changes in main will go into a future update of MSBuild, which will release with Visual Studio 17.0 and a corresponding version of the .NET Core SDK.

Build Status

We have forked for MSBuild 16.11 in the branch vs16.11. Changes to that branch need special approval.

Build Status

MSBuild 16.9 builds from the branch vs16.9. Only high-priority bugfixes will be considered for servicing 16.9.

Build Status

MSBuild 16.7 builds from the branch vs16.7. Only high-priority bugfixes will be considered for servicing 16.7.

Build Status

MSBuild 16.4 builds from the branch vs16.4. Only high-priority bugfixes will be considered for servicing 16.4.

Build Status

MSBuild 15.9 builds from the branch vs15.9. Only very-high-priority bugfixes will be considered for servicing 15.9.


Building MSBuild with Visual Studio 2019 on Windows

For the full supported experience, you will need to have Visual Studio 2019 or higher.

To get started on Visual Studio 2019:

  1. Install Visual Studio 2019. Select the following Workloads:
  • .NET desktop development
  • .NET Core cross-platform development
  1. Open a Developer Command Prompt for VS 2019 prompt.
  2. Clone the source code: git clone
  1. Run .\build.cmd from the root of the repo to build the code. This also restores packages needed to open the projects in Visual Studio.
  2. Open MSBuild.sln or MSBuild.Dev.slnf in Visual Studio 2019.

Note: To create a usable MSBuild with your changes, run .\build.cmd /p:CreateBootstrap=true. To build release, add -c Release: .\build.cmd -c Release /p:CreateBootstrap=true.

This newly-built MSBuild will be located at artifacts\bin\bootstrap\net472\MSBuild\Current\Bin\MSBuild.exe. It may not work for all scenarios, including C++ builds.

Building MSBuild in Unix (Mac & Linux)

MSBuild can be run on Unix systems that support .NET Core. Set-up instructions can be viewed on the wiki: Building Testing and Debugging on .Net Core MSBuild


You can turn on localized builds via the /p:LocalizedBuild=true command line argument. For more information on localized builds and how to make contributions to MSBuild's translations, see our localization documentation

Getting Started

Before you contribute, please read through the contributing and developer guides to get an idea of what kinds of pull requests we accept.

Looking for something to work on? This list of up for grabs issues is a great place to start.

You are also encouraged to start a discussion by filing an issue or creating a gist.

MSBuild Components

  • MSBuild. Microsoft.Build.CommandLine is the entrypoint for the Microsoft Build Engine (MSBuild.exe).

  • Microsoft.Build. The Microsoft.Build namespaces contain types that provide programmatic access to, and control of, the MSBuild engine.

  • Microsoft.Build.Framework. The Microsoft.Build.Framework namespace contains the types that define how tasks and loggers interact with the MSBuild engine. For additional information on this component, see our Microsoft.Build.Framework wiki page.

  • Microsoft.Build.Tasks. The Microsoft.Build.Tasks namespace contains the implementation of all tasks shipping with MSBuild.

  • Microsoft.Build.Utilities. The Microsoft.Build.Utilities namespace provides helper classes that you can use to create your own MSBuild loggers and tasks.


MSBuild is licensed under the MIT license.