Aspire 13.6.0 is now available
The dotnet/aspire repository published v13.6.0 on 2026-09-29. The release notes list changes including: 🗃️ Persistent, refreshed dashboard — SQLite-backed telemetry and resource snapshots let you revisit up to ten application runs, with read-only access to…; 🖥️ AppHost-owned terminals and database REPLs — Experimental….
What was released From the source
dotnet/aspire published v13.6.0 on GitHub on 2026-09-29. Items listed in the release notes include:
- 🗃️ Persistent, refreshed dashboard — SQLite-backed telemetry and resource snapshots let you revisit up to ten application runs, with read-only access to…
- 🖥️ AppHost-owned terminals and database REPLs — Experimental terminal APIs let AppHosts create interactive sessions in a dashboard dock, dialog, or separate…
- 🌐 First-party Java and Rust hosting — New Aspire.Hosting.Java and Aspire.Hosting.Rust packages bring Maven, Gradle, Spring Boot, Quarkus, and Cargo…
- 🛠️ More flexible AppHosts — The prerelease Aspire.Hosting.Dotnet integration coordinates compatible projects into shared restore and build groups and…
- ⌨️ Sharper CLI workflows — Select launch profiles with aspire run and aspire start, update repository-local CLI manifests with aspire update, create…
- 💻 More capable VS Code tooling — Coding agents can start and stop AppHosts through the extension, and the Aspire pane exposes deploy, publish, and pipeline…
- ☁️ New Azure options in preview — Azure Connector Namespace models external-service connections and managed MCP server configurations. Azure Container Apps…
- ☸️ More expressive, reliable deployments — Experimental Azure Provisioning SDK proxies let polyglot AppHosts customize infrastructure. Deployment state is…
At a glance · Azure
What was releasedWhy it mattersWho should careUpgrade considerations
Why it matters Analysis
Azure service changes can affect how .NET applications are hosted, scaled and connected to data and AI services. Knowing about previews, general availability and SDK updates helps teams plan adoption and avoid surprises in production.
Who should care Analysis
- .NET developers deploying to Azure
- Cloud architects and platform engineers
- Teams using the Azure SDK for .NET
Upgrade considerations Analysis
- Read the complete release notes for breaking changes and known issues.
- Update the relevant NuGet packages in a branch and run your tests before merging.
- Check whether a preview feature is suitable for production workloads.
- Update Azure SDK packages and test in a non-production subscription first.
Sources and further reading
- Release notes for v13.6.0 on GitHub (original source)
Original: “Aspire 13.6.0”, Aspire releases, published 29 Sep 2026, retrieved 16 Oct 2026. This article was generated from the official source using our structured templates and passed automated quality checks. Spotted a mistake? See our corrections policy.