# Simplifying .NET toolchain installs with dotnetup

DevFeed: [Simplifying .NET toolchain installs with dotnetup](<https://devfeed.tech/articles/simplifying-net-toolchain-installs-with-dotnetup-106249.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4241187/simplifying-net-toolchain-installs-with-dotnetup.html>)

Author: Simon Bisson

Published: 2026-10-29T09:00:00Z

Content type: article

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [.NET](<https://devfeed.tech/topics/net.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [asp-net](<https://devfeed.tech/tags/asp-net.md>), [asp-net-core](<https://devfeed.tech/tags/asp-net-core.md>), [aspire](<https://devfeed.tech/tags/aspire.md>), [automated](<https://devfeed.tech/tags/automated.md>), [build-tools](<https://devfeed.tech/tags/build-tools.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cli](<https://devfeed.tech/tags/cli.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [container](<https://devfeed.tech/tags/container.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [development](<https://devfeed.tech/tags/development.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [development-tools-libraries-and-frameworks-microsoft-net-software-development](<https://devfeed.tech/tags/development-tools-libraries-and-frameworks-microsoft-net-software-development.md>), [dotnetup](<https://devfeed.tech/tags/dotnetup.md>), [ephemeral-environments](<https://devfeed.tech/tags/ephemeral-environments.md>), [github](<https://devfeed.tech/tags/github.md>), [github-action](<https://devfeed.tech/tags/github-action.md>), [installation](<https://devfeed.tech/tags/installation.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [libraries-and-frameworks](<https://devfeed.tech/tags/libraries-and-frameworks.md>), [linux](<https://devfeed.tech/tags/linux.md>), [microsoft-net](<https://devfeed.tech/tags/microsoft-net.md>), [net](<https://devfeed.tech/tags/net.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-analysis](<https://devfeed.tech/tags/storytype-analysis.md>), [toolchain](<https://devfeed.tech/tags/toolchain.md>)

## AI overview

dotnetup is a public-preview command-line tool for installing and managing .NET SDKs and runtimes in user-owned directories, with separate versions and configurable tool selections. The excerpt reports successful installs on Windows, macOS, and Ubuntu, though defaults differed by OS: Windows included .NET 9 and 10 SDKs and more runtimes, while macOS and Linux installed .NET 10; ASP.NET could not be installed on the tested Mac. Windows offers "everywhere" mode for setting machine-wide PATH and DOTNET_ROOT, while macOS and Linux offer "none" or shell-scoped environments. Developers can select channels or specific SDK versions, define installation roots, and migrate an existing environment; system-level .NET directories cannot be used as roots. Its noninteractive operation supports CI pipelines, including GitHub Actions, where dotnetup can install a chosen SDK for builds and tests. The preview still lacks support for some runtimes and extensions, such as Aspire and .NET WebAssembly, and does not yet integrate with Visual Studio Code.

## Source excerpt

If you've experimented with Rust, you already know how simple it is to get a basic toolchain in place, with the simple rustup command-line tool. The same tool works on Windows, macOS, and Linux, building a consistent environment that's ready for you to pick up your favorite coding editor and start work. It's a simple enough tool, and one that's done much to help popularize a new programming language. With rustup, you know what you're getting, and you can start working on any laptop, anywhere. Managing .NET environments is complex Things are not so simple with .NET. Yes, it's cross platform, running on Windows, macOS, and Linux. However, it's not so easy to set up, often relying on third-party repositories and installers, as well as many different scripts that install different versions and their associated platforms. Have you installed ASP.NET Core? Do you need Aspire, or are you building a mobile application with MAUI? Everything has its own custom install route, which will likely differ depending on the target OS. To cap it off, .NET tools often need to be run with the highest level of privileges needed, requiring developers to have administrative rights. None of that is particularly developer friendly, and it makes it hard to build .NET tooling into ephemeral environments like CI/CD build tools and runners, where you need to populate a hosted container for test and compilation, loading a new instance of the .NET CLI every time you fire up a GitHub Action -- and having to run tooling with a much higher set of privileges than you want for an automated process. Things get more confusing when you're maintaining an application with a current build of .NET at the same time as updating it for the next long-term release, all on the same development workstation. With platform-specific toolchains and installation mechanisms, complexity gets in the way of coding and .NET becomes less of a priority, despite its cross-platform features and its maturity. It's clearly time for a