咨询：MSBuild是否计划支持.NET Core项目？还有哪些构建引擎兼容？

Hey there! Awesome questions—let me clear this up for you since you’ve been digging into outdated resources:

Good news: MSBuild has fully supported .NET Core (and later .NET 5+) for years—there’s no "planned support" needed because it’s been integrated into the .NET ecosystem since the early days of .NET Core 1.0.

In fact, when you run commands like dotnet build or dotnet publish for your .NET Core apps, you’re actually leveraging MSBuild under the hood. You can also use MSBuild directly via its command-line tool (either msbuild.exe on Windows, or msbuild on Linux/macOS) or through Visual Studio’s build system, which all work seamlessly with .NET Core projects. The unified .NET SDK (starting with .NET 5) further ties MSBuild into the core tooling, so it’s the default build engine for all modern .NET projects.

If you’re looking for alternatives to MSBuild, here are some popular options that work great with .NET Core:

• dotnet CLI: While it relies on MSBuild under the hood, it’s a dedicated, simplified command-line tool built specifically for .NET Core/.NET. Commands like dotnet build, dotnet test, and dotnet publish are staple tools for everyday .NET development.
• Nuke Build: A powerful .NET-native build automation tool that lets you write build scripts in C#. It’s highly flexible, perfect for complex build pipelines, and fully supports all .NET versions including .NET Core.
• FAKE (F# Make): A functional-first build tool written in F#. It has a concise, expressive syntax and handles all stages of .NET Core development—from building and testing to publishing and deployment.
• Cake: A cross-platform build automation tool that uses C# for scripting. It has a large ecosystem of add-ons, integrates with most DevOps tools, and works smoothly with .NET Core projects.
• Paket: Primarily a package manager (alternative to NuGet), but it integrates tightly with build workflows (often paired with FAKE) and fully supports .NET Core.

内容的提问来源于stack exchange，提问作者Kevin Bindig