.NET Aspire 17.0 shipped on November 17 with a clear ask: upgrade your AppHost to .NET 10 or stay on 13.6. That’s not a suggestion — the new version drops .NET 8 and .NET 9 support entirely for the AppHost project. If you’re not yet on .NET 10, this release isn’t for you yet. If you are, you get stable Kubernetes deployment, Go AppHosts in preview, a redesigned dashboard, and a tray companion that finally stops you from hunting through terminals to find your services.
The .NET 10 Floor Is Real — Here’s What Breaks
The AppHost project must target .NET 10. That’s the hard requirement. The good news: the services you orchestrate — your APIs, workers, and databases — don’t have to retarget. .NET 8 and .NET 9 workloads can still run; only the AppHost itself needs to move up.
Beyond the minimum version, Aspire 17 removes a handful of things that have been deprecated for a while. AddProject, AddCSharpApp, and Aspire.AppHost.Sdk are deprecated in favor of path-based AddDotnetProject. The RabbitMQ v6 and MongoDB v2 integrations are gone — replaced by current-version packages. And here’s one that will catch teams off guard: empty required parameter values, previously accepted silently, are now rejected. If your AppHost uses AddParameter with optional empty values, audit those before upgrading.
The community friction on GitHub is real. Multi-target projects hit restore failures; teams with .NET 8 test integrations found breakages. The upgrade path exists, but it’s not frictionless.
Kubernetes Is Stable — Finally
Aspire.Hosting.Kubernetes and Aspire.Hosting.Azure.Kubernetes both ship as stable packages in Aspire 17. This matters because “experimental” in a production deployment story is a red flag. Those packages are no longer experimental.
What you get with the stable packages: generate Helm charts from your AppHost definition, deploy via aspire deploy or your own pipeline, and target pre-provisioned AKS clusters without reconfiguring node pools, networking, or add-ons. The AsExisting APIs handle existing-resource scenarios cleanly.
Two things to watch before upgrading your Kubernetes deployments. First, Helm 4.0+ is now required — Helm 3 won’t work. Second, the default AKS control-plane tier shifts from Free to Standard, which carries a cluster-management cost for new clusters Aspire provisions. Existing clusters aren’t affected unless you redeploy infrastructure. The full Aspire Kubernetes deployment guide covers migration steps.
Go AppHosts Are in Preview
Go support in Aspire moves from experimental to preview in this release. The experimental flag is gone — run aspire new and Go templates show up natively alongside C#. Two starting points: aspire-go-empty and aspire-go-starter. Add Go to an existing app with aspire init --language go.
Debugging works properly: VS Code’s Go extension with the Delve adapter gives you F5 step-through on apphost.go. The Aspire view in VS Code lets you attach the debugger to running Go or .NET resources. aspire doctor now checks for Go tooling and reports missing dependencies.
The bigger picture here is polyglot orchestration. Teams running Go services alongside .NET APIs can now bring everything under one Aspire AppHost — same dashboard, same observability, same deployment pipeline. That’s genuinely useful for mixed-stack shops. Microsoft’s Aspire 17 release notes cover the full Go preview feature set.
The Dashboard Gets a Proper Redesign
The dashboard lands a resource-first home page — the resources table is now the default landing view instead of a summary overview. It’s a small change that makes the daily workflow noticeably faster.
Two additions worth calling out. The Terminals page gets its own spot in the navigation bar, pulled out of Console logs where it was awkward to find. And resource dependency graphs can now be exported as Mermaid diagrams — from the dashboard UI (Export as Mermaid button) or via CLI (aspire resources --format mermaid). That’s immediately useful for documenting service relationships in wikis or architecture docs.
Terminal windows also auto-fit to available viewport on open — no more clicking “Fit” after the terminal renders at a fixed size from startup.
Team Configuration Source and Tray Companion
Two smaller additions that target different users. For platform teams: set ASPIRE_INIT_SOURCE_URL to a Git repo containing your org’s Aspire defaults. When a developer runs aspire init, the CLI surfaces the team source and asks for consent before adopting it. This standardizes Aspire configuration across teams without force-applying anything.
For individual developers: aspire tray start adds running AppHosts to the macOS menu bar, Windows notification area, or Linux desktop tray. Health status, a dashboard link, stop controls — all without opening another terminal window. It’s in preview, but it’s the kind of quality-of-life improvement that disappears into the background once you’re used to it.
Should You Upgrade?
If your AppHost is on .NET 10: yes. The stable Kubernetes packages, Go preview support, and dashboard improvements are worth it. Audit your AddParameter usage for empty values before you do. Full details in the Aspire 17.0.0 GitHub release and the official what’s new guide.
If you’re on .NET 8 or 9: not yet. Wait until your AppHost project moves to .NET 10. The features will still be there.

