Commands
These pages define the product-level behavior of each operation. They intentionally do not repeat complete PowerShell and Bash invocation syntax.
- Install — install one exact SDK under the isolated SDK root
- List — show Isolated SDKs and read-only System SDKs
- Audit — assess installed SDK servicing and lifecycle state against current Microsoft metadata
- Verify — perform a read-only health check of one isolated SDK
- Remove — remove one SDK managed under the isolated SDK root
- Tool version — identify the running tool release or development source
- Interactive mode — persistent sessions, navigation, and SDK selection
- Troubleshooting and safe recovery — failure symptoms, safe next actions, and recovery boundaries
For exact commands and copy/paste examples, use the supported platform guide:
Shared command model
Starting the tool without an action or exact version opens the persistent interactive session. Explicit actions and exact-version requests are one-shot and exit after the requested operation completes, is cancelled normally, or fails.
The tool-version query is also one-shot, but it identifies isolated-dotnet-sdk itself rather than selecting a .NET SDK. It exits before bootstrap, SDK discovery, release-metadata access, prompting, or mutation. PowerShell uses -Version and Bash uses --version for tool identity. Exact SDK selection is -SdkVersion <version> in PowerShell and --sdk-version <version> in Bash, and both shells also accept the exact SDK version positionally.
The tool owns SDKs only under the current user’s dotnet-sdks directory. System SDKs are supplemental read-only inventory and never become removable merely because the tool can see them. List remains network-independent; Verify’s local proof is authoritative but optional Microsoft release/lifecycle enrichment can use the network. Audit is the explicit online read-only operation for servicing and lifecycle assessment.
For detailed cross-shell behavior and intentional platform differences, see PowerShell and Bash behavioral parity.