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 docs.microsoft.com.
The current development branch is master. Changes in master will go into a future update of MSBuild, which will release with Visual Studio 16.7 and a corresponding version of the .NET Core SDK.
We have forked for MSBuild 16.6 in the branch vs16.6. Changes to that branch need special approval.
MSBuild 16.4 builds from the branch vs16.4. Only high-priority bugfixes will be considered for servicing 16.4.
MSBuild 16.0 builds from the branch vs16.0. Only high-priority bugfixes will be considered for servicing 16.0.
MSBuild 15.9 builds from the branch vs15.9. Only very-high-priority bugfixes will be considered for servicing 15.9.
| Runtime\OS | Windows | Ubuntu 16.04 | Mac OS X |
|---|---|---|---|
| Full Framework | N/A | N/A | |
| .NET Core |
For the full supported experience, you will need to have Visual Studio 2019 or higher.
To get started on Visual Studio 2019:
- Install Visual Studio 2019. Select the following Workloads:
- .NET desktop development
- .NET Core cross-platform development
- Open a
Developer Command Prompt for VS 2019prompt. - Clone the source code:
git clone https://github.com/Microsoft/msbuild.git
- You may have to download git first.
- Run
.\build.cmdfrom the root of the repo to build the code. This also restores packages needed to open the projects in Visual Studio. - Open
MSBuild.slnorMSBuild.Dev.slnin Visual Studio 2019.
Note: To create a usable MSBuild with your changes, run .\build.cmd /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.
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
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Before you contribute, please read through the contributing and developer guides to get an idea of what kinds of pull requests we accept.
-
Developer Guide on:
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. 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.