Aspire 13.5.0 is now available
The dotnet/aspire repository published v13.5.0 on 2026-08-18. The release notes list changes including: 💬 Richer AppHost interactions — The Interaction Service now works across C# and TypeScript AppHosts with stable prompts and dynamic inputs, file uploads…; 🖥️ Interactive terminal sessions — The experimental….
What was released From the source
dotnet/aspire published v13.5.0 on GitHub on 2026-08-18. Items listed in the release notes include:
- 💬 Richer AppHost interactions — The Interaction Service now works across C# and TypeScript AppHosts with stable prompts and dynamic inputs, file uploads…
- 🖥️ Interactive terminal sessions — The experimental WithTerminal() API lets resources host REPLs, shells, TUIs, and other interactive programs directly in…
- 🌐 TypeScript AppHost is generally available — Polyglot AppHosts no longer require the ASPIREATS001 experimental diagnostic and gain custom health checks…
- 🛠️ CLI installation and reliability — The Aspire CLI is available through npm and Nix alongside Homebrew, WinGet, mise, and NuGet. New C# AppHosts enable the…
- 🎨 Refreshed dashboard — The dashboard adopts official Aspire branding and a new accessible design-token system, with timestamp and exact numeric telemetry…
- 💻 Rebranded VS Code extension — The extension is now named Aspire and adds an in-editor dashboard, Bun and MAUI debugging, resource commands in the tree…
- ☸️ More expressive deployments — Kubernetes and AKS gain first-class persistent volumes, Azure Container Apps adds deterministic unique resource naming, Azure…
- ☁️ Expanded hosting integrations — Azure resources can be referenced across resource groups, subscriptions, and tenants; the new Aspire.Hosting.Dotnet package…
At a glance · Runtime & Platform
What was releasedWhy it mattersWho should careUpgrade considerations
Why it matters Analysis
Changes to the .NET runtime, libraries and application frameworks shape performance, compatibility and the features available to every .NET application. Following them helps teams plan upgrades and adopt improvements deliberately.
Who should care Analysis
- .NET application developers
- Library and framework authors
- Teams planning .NET version upgrades
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.
- Try new features or previews in a test project first.
- Check the .NET breaking-changes documentation before upgrading major versions.
Sources and further reading
- Release notes for v13.5.0 on GitHub (original source)
Original: “Aspire 13.5.0”, Aspire releases, published 18 Aug 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.