Tool version
The tool exposes its own release/source identity separately from the .NET SDK versions it installs and manages.
Direct query
Both supported shells use their native version switch for the tool itself:
& "$HOME\dotnet-sdks\isolated-dotnet-sdk.ps1" -Version
"$HOME/dotnet-sdks/isolated-dotnet-sdk.sh" --version
A stable copy published with embedded identity reports its exact release tag, for example:
isolated-dotnet-sdk v1.2.3
A copy sourced from mutable main reports development identity instead:
isolated-dotnet-sdk development (main)
The version query exits successfully after printing that identity. It does not bootstrap or replace the saved tool, create the isolated SDK root, query release metadata, enumerate SDKs, prompt for input, or check whether a newer release exists.
Tool version versus SDK version
The supported shells expose the same version-selection capabilities with native switch spelling:
| Purpose | PowerShell | Bash |
|---|---|---|
| Tool release/source identity | -Version |
--version |
| Explicit exact SDK selector | -SdkVersion <version> |
--sdk-version <version> |
| Positional exact SDK selector | <version> |
<version> |
The explicit and positional SDK forms are equivalent. With no explicit action, an SDK version is a one-shot Install request. With Install, Verify, or Remove, it selects the SDK for that action.
-Version / --version never selects a .NET SDK. It identifies the isolated-dotnet-sdk tool itself.
Stable and development identity
Stable releases published under this identity model embed the exact release tag into both supported product scripts during release publication. The checksum manifest is generated from those stamped release bytes, so tagged source, latest-stable bootstrap, pinned bootstrap/rollback, and the saved copy all retain the same identity.
Mutable main carries an explicit development identity and never derives or claims the latest published stable version.
Historical releases are not rewritten solely to add embedded identity metadata. A release published before this model remains historically unchanged.
The persistent Main menu displays the same underlying identity in a friendlier heading.