On this page Overview
.NET SDK Manager documentation
Every .NET SDK, one keyboard away.
A cross-platform terminal UI for managing .NET SDKs and Runtimes. Install, update, search, and remove — all from a single keyboard-driven interface.
Choose your path
- Install dsm One command on macOS, Linux, or Windows — a self-contained native binary, no .NET runtime required.
- Tour the .NET workspace Launch dsm, set up dotnetup, migrate the SDKs you already have, then install, search, manage workloads, and uninstall — with real screenshots.
- Learn the shortcuts Everything is keyboard-driven. Keep the cheat sheet handy.
- Contribute Build from source, run the tests, and open a pull request.
Everything in one screen
No context switching. See your installed SDKs, available updates, runtimes, and search results — all at a glance.
View installed SDKs alongside the latest available versions. Install, uninstall, and update with a single keystroke.
Already have .NET installed outside dotnetup? dsm flags it as Unmanaged and brings it under management — one SDK with m, or all of them with Shift+M.
Full visibility into .NET and ASP.NET Core runtimes. Same install/uninstall/update workflow as SDKs.
Non-blocking search with debounce. Type to search, results update as you go. Previous requests are automatically cancelled.
Press F6 to toggle. The terminal background adapts automatically for a native look in both modes.
dsm pins your other installed versions before every install or uninstall, so dotnetup’s cleanup only ever removes the version you selected.
Compiled ahead-of-time for instant startup. Small binary, no runtime dependency required on the target machine.
Installation
One command to install. No .NET runtime needed — it's a self-contained native binary. Running the same command again updates to the latest version.
Works on Bash, Zsh, and Fish. Installs to ~/.local/bin and adds it to your PATH automatically.
curl -fsSL https://raw.githubusercontent.com/shahabganji/dotnet-sdk-tui/main/install/install.sh | bash
curl -fsSL https://raw.githubusercontent.com/shahabganji/dotnet-sdk-tui/main/install/uninstall.sh | bash
PowerShell 7+ or Windows PowerShell 5.1. Installs to %LOCALAPPDATA%\dsm and adds it to your user PATH.
irm https://raw.githubusercontent.com/shahabganji/dotnet-sdk-tui/main/install/install.ps1 | iex
irm https://raw.githubusercontent.com/shahabganji/dotnet-sdk-tui/main/install/uninstall.ps1 | iex
Native builds for macOS, Linux and Windows on both x64 and ARM64. Linux builds need glibc 2.27 or newer (Ubuntu 18.04+, Debian 10+, RHEL 8+, Fedora…); Alpine/musl isn't supported yet. On Windows, dsm shows symbols instead of emoji icons. Set DSM_VERSION=v0.9.3 to install a specific release.
After installation, open a new terminal and run dsm. The app will notify you when updates are available — press Ctrl+U to self-update.
Prerequisites
dsm uses dotnetup, the official .NET SDK acquisition tool, for installing and managing SDKs and runtimes. You can install dotnetup from within dsm (press i in the Setup panel; on Windows this runs dotnetup's installer with PowerShell 7 when it's installed, otherwise Windows PowerShell), or set it up manually by following the dotnetup documentation.
Troubleshooting
killed / “killed: 9” after updatingIf dsm exits immediately with killed (signal 9) right after an update, an older installer replaced the binary in place, which invalidates its code signature on macOS. Re-run the install command to fix it — the installer now replaces the binary atomically, so future updates are safe:
curl -fsSL https://raw.githubusercontent.com/shahabganji/dotnet-sdk-tui/main/install/install.sh | bash
Keyboard shortcuts
Everything is keyboard-driven. No mouse needed.
The .NET step-by-step guide shows every flow with real screenshots — launching dsm, installing dotnetup, migrating SDKs you already have, installing & searching for SDKs, managing workloads per SDK, and uninstalling versions.
| Key | Action |
|---|---|
| ↑ / ↓ or j / k | Navigate rows |
| Tab | Cycle focus between SDKs, Runtimes, and Setup panels |
| i | Install selected SDK, Runtime, or Workload |
| u | Uninstall selected SDK, Runtime, or Workload |
| p | Update to latest in the channel (SDKs/Runtimes) or update all workloads |
| w | Open the Workloads workspace for the selected installed SDK |
| Shift+P | Repair workloads (Workloads workspace) |
| m | Migrate the selected unmanaged or other-location SDK; toggle workload update-mode (Workloads workspace) |
| Shift+M | Migrate all unmanaged and other-location SDKs (with confirmation) |
| D | Delete the selected other-location SDK or runtime (with confirmation) |
| f | Forget the remembered install folder (Setup panel) |
| r | Refresh data from the network |
| F3 | Open the search screen |
| F6 | Toggle dark / light theme |
| Ctrl+U | Self-update dsm to latest version |
| Esc | Return to main screen from a workspace |
| q or Ctrl+C | Quit |
Search syntax
Open search with F3, then just start typing. Results update live with debounce — no enter key needed.
# Search by channel version
/ Search: 10 # Shows all .NET 10 SDKs and runtimes
# Search by keyword
/ Search: preview # Shows all preview/RC versions
/ Search: latest # Shows latest versions across supported channels
/ Search: lts # Shows long-term support versions
Command line
dsm # Launch with animated banner
dsm --no-splash # Skip the banner animation
dsm --version # Print version and exit
Build from source
Requires the .NET 10 SDK or later.
# Clone the repository
git clone https://github.com/shahabganji/dotnet-sdk-tui.git
cd dotnet-sdk-tui
# Run in development
dotnet run --project src/DotnetSdkTui
# Run tests
dotnet test
# Publish a NativeAOT binary
dotnet publish src/DotnetSdkTui -c Release -r osx-arm64
Contributing
Contributions are welcome! Here's how to get involved.
- Fork & clone
Fork the repository and clone it locally.
- Branch
Create a branch from
mainfor your feature or fix. - Build & test
Run
dotnet testto make sure everything passes. - Open a PR
Submit a pull request with a clear description of your changes.
Areas where help is appreciated
- New platform support — test and report issues on platforms you use
- Accessibility — keyboard navigation, screen reader improvements
- Themes — new color palettes or refinements
- Offline mode — better UX without network connectivity
- Bug reports — if something doesn't work, let us know