Isolated .NET SDK Exact SDKs without changing system .NET

Releases

Stable bootstrap

The normal stable installation/update path resolves the latest published stable release at bootstrap time:

irm https://infoconex.github.io/isolated-dotnet-sdk/install.ps1 | iex

curl -fsSL https://infoconex.github.io/isolated-dotnet-sdk/install.sh | bash

Use Stable bootstrap, update, and rollback for the trust model, explicit pinned-version procedure, update behavior, and rollback guidance. Platform-specific usage continues in:

Release history

Release-history pages summarize prepared and published stable releases for users. A history page may be committed before its public release; GitHub Releases is authoritative for publication status. For the chronological categorized change log, see the project CHANGELOG.

  • v0.4.0 release history — historical SDK compatibility, safer removal, richer verification, and interactive UX hardening.
  • v0.3.0 release history — verified latest-stable bootstrap, explicit tool identity, SDK Audit, interactive Verify, and stronger release verification.
  • v0.2.0 release history — first stable release under the checksum-verifying release policy.
  • v0.1.0 release history — initial release and legacy pre-checksum-policy behavior.

The v0.1.0 release checklist remains available as legacy release-process history.

Maintainers

Publication and post-publication verification procedure is intentionally separate from user bootstrap guidance. Maintainers should use Stable release publication and verification.