dotnet-msbuild(1)

💅 dotnet-msbuild(1) — the .NET Documentation girlies know

okay so bestie, welcome to the dotnet-msbuild(1) page from the .NET Documentation set. it's giving "MSBuild but make it dotnet", and honestly? iconic. ✨

📌 this article applies to: ✔️ .NET 6 SDK and later versions

---

🌸 NAME 🌸

dotnet-msbuild — builds a project and all of its dependencies.

💀 real talk though: a solution or project file may need to be specified if there are multiple. not me forgetting that and staring at my terminal like 👁️👄👁️

---

✨ SYNOPSIS ✨

dotnet msbuild <MSBUILD_ARGUMENTS>

dotnet msbuild -h

---

🎀 DESCRIPTION 🎀

so the dotnet msbuild command gives you access to a fully functional MSBuild. the whole thing. the full serve. no cap. 🔥

it has the exact same capabilities as the existing MSBuild command-line client — but for SDK-style projects only. the options are all the same, fr fr. and if you wanna know about all the available options, go check the MSBuild command-line reference. iykyk 📖✨

and here's the tea 🍓: the dotnet build command is equivalent to dotnet msbuild -restore.

💡 that's literally the same thing, just with the restore already baked in. main character energy.

---

🌈 EXAMPLES 🌈

okay bestie, let's get into the good stuff 👑

1. Build a project and its dependencies:

dotnet msbuild

2. Build a project and its dependencies using Release configuration:

dotnet msbuild -property:Configuration=Release

3. Run the publish target and publish for the osx-x64 RID:

dotnet msbuild -target:Publish -property:RuntimeIdentifiers=osx-x64

4. See the whole project with all targets included by the SDK:

dotnet msbuild -preprocess
dotnet msbuild -preprocess:<fileName>.xml

---

and that's the whole vibe check, bestie 🦋 this one's from the .NET Documentation source, dated 2025-10-30, and you already know the manual name — it's dotnet-msbuild(1) 💖 go build something cute, and remember: <MSBUILD_ARGUMENTS> are your besties. periodt. 💅✨