Simplifying .NET Installs with dotnetup
TL;DR
dotnetup is meant to replace today's .NET install mess with one supported flow: Chad Husk frames the problem as "Visual Studio on Windows" versus "everyone else," where developers bounce between Visual Studio Code, Homebrew, distro packages, install scripts, DNVM, asdf, and manual zip or tarball installs.
The core promise is simple repo setup from global.json: in the demo,
dotnetup initinstalls the latest SDK into the user's home directory, anddotnetup sdk installreads a repo'sglobal.jsonto fetch the right feature band, such as moving from .NET 10.3xx to 10.1xx when rollForward changes tolatestPatch.It tracks intent, not just installed bits:
dotnetup listshows installed SDKs, tracked channels, and why they exist, so a futuredotnetup updatecan automatically move a machine forward when new versions like 10.9 or 10.10 ship.Runtime-only installs fix a common wasteful CI pattern: Husk shows tests targeting .NET 8, 9, and 10 failing on a machine with only .NET 10 runtimes, then fixes it with
dotnetup runtime install 8.0 9.0 10, avoiding full parallel SDK installs that can each cost hundreds of megabytes.Microsoft is designing this as much for agents as for humans: the tool is built to run without admin rights, add guard rails for AI and CI setup, and eventually publish agent skills so automated systems can install, update, and compare SDK versions safely.
The roadmap goes beyond installs into supply chain trust and componentized tooling: planned milestones include daily SDK support, one-shot execution for A/B testing versions, self-update, update notifications, full signature verification, runtime declarations in
global.json, and longer-term integration into GitHub Actionssetup-dotnetand Azure DevOpsUseDotNet.
The Breakdown
Microsoft is trying to make "clone repo, run one command, and be good to go" the default .NET setup experience with dotnetup, a new cross-platform installer and version manager that works in user space without admin rights. Chad Husk shows early previews of SDK and runtime installs, automatic tracking of what each repo needs, and a roadmap that pulls humans, CI systems, and AI agents onto the same supported path.
Was This Useful?
Share
Keep Reading
Make Alcreon Yours
Tune your feedFive quick questions, and the feed ranks what matters to you first.Or just get notified
The weekly Echo. Signal worth keeping in your inbox.
Every new piece, announced on X.
Read Next
See all
Playbook
Tasteful Skills
“Tasteful Skills” argues that the best agent skills are not documentation or best-practice lists.

Playbook
The Art of Tasteful Prompting
Learn how tasteful prompting helps you move beyond generic AI output by shaping context, style, and judgment from the start.

Playbook
The Codex /goal Playbook
OpenAI shipped /goal for the Codex CLI. It turns a prompt into a persisted, self-continuing contract.