MSBuild alternatives and similar packages
Based on the "Build Automation" category.
Alternatively, view MSBuild alternatives based on common mentions on social networks and blogs.
Cake8.8 9.0 L3 MSBuild VS Cake:cake: Cake (C# Make) is a cross platform build automation system.
NUKE7.4 7.9 MSBuild VS NUKE🏗 The AKEless Build System for C#/.NET
FAKE7.3 6.9 MSBuild VS FAKEFAKE - F# Make
Psake7.2 0.0 MSBuild VS PsakeA build automation tool written in PowerShell
FlubuCore6.0 5.1 MSBuild VS FlubuCoreA cross platform build and deployment automation system for building projects and executing deployment scripts using C# code.
Invoke-Build5.1 2.8 MSBuild VS Invoke-BuildBuild Automation in PowerShell
Albacore3.9 0.0 L5 MSBuild VS AlbacoreAlbacore is a professional quality suite of Rake tasks for building .NET or Mono based systems.
Nake3.5 1.3 L4 MSBuild VS NakeMagic script-based C# task runner for .NET Core
CS Make2.9 0.0 L5 MSBuild VS CS MakeSake Build
NUKE/common2.4 0.0 MSBuild VS NUKE/commonBuild System for C#/.NET
EmptyLicensesLicx2.4 3.3 MSBuild VS EmptyLicensesLicxEasy continuous integration of apps using third-party controls that rely on licenses.licx files
Build Versioning1.9 0.0 MSBuild VS Build VersioningSimple build versioning for .NET, powered by Git tags
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of MSBuild or a related project?
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 [changelog](documentation/Changelog.md) has detailed information about changes made in different releases.
The current development branch is
main. Changes in
main will go into a future update of MSBuild, which will release with Visual Studio 17.5 and a corresponding version of the .NET Core SDK.
We have forked for MSBuild 17.4 in the branch
vs17.4. Changes to that branch need special approval.
17.2 builds from the branch
vs17.2. Only high-priority bugfixes will be considered for servicing 17.2.
17.0 builds from the branch
vs17.0. Only high-priority bugfixes will be considered for servicing 17.0.
16.11 builds from the branch
vs16.11. Only high-priority bugfixes will be considered for servicing 16.11.
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 2022 on Windows
For the full supported experience, you will need to have Visual Studio 2022 or higher.
To get started on Visual Studio 2022:
- Install Visual Studio 2022. Select the following Workloads:
- .NET desktop development
- .NET Core cross-platform development
- Ensure long path support is enabled at the Windows level.
- Open a
Developer Command Prompt for VS 2022prompt.
- Clone the source code:
git clone https://github.com/dotnet/msbuild
- You may have to download Git first.
.\build.cmdfrom the root of the repo to build the code. This also restores packages needed to open the projects in Visual Studio.
MSBuild.Dev.slnfin Visual Studio 2022.
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](documentation/wiki/Building-Testing-and-Debugging-on-.Net-Core-MSBuild.md)
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](documentation/wiki/Localization.md)
Interested in contributing?
Before you contribute, please read through the contributing and developer guides to get an idea of what kinds of pull requests we accept.
- [Contributing Guide](documentation/wiki/Contributing-Code.md)
Developer Guide on:
- [.NET Core](documentation/wiki/Building-Testing-and-Debugging-on-.Net-Core-MSBuild.md)
- [Full Framework](documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md)
See our help wanted issues for a list of issues we think are great to onboard new developers.
- Note: Please leave a comment asking to be assigned the issue if you want to work on it.
See our [label documentation](documentation/wiki/Labels.md) for descriptions of labels we use throughout the repo.
Other ways to contribute
We encourage any contributions you decide to make to the repo!
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](documentation/wiki/Microsoft.Build.Framework.md).
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](LICENSE).
*Note that all licence references and agreements mentioned in the MSBuild README section above are relevant to that project's source code only.