Learn what is new in the latest Visual Studio Code Insiders build, including agent session management and editor tab improvements.
Aspire 17 is here! 
Back in June (which is basically an eternity ago), we sat down to plan the next few months of Aspire. We were excited to realize we’d already shipped most of the roadmap we’d planned the year before. But… what comes next? We’d flown through it faster than we’d expected.
As we sketched out the next roadmap, we looked at what you were building with Aspire, including the growing number of teams adopting it here at Microsoft.
You were running dozens of services in one AppHost, sharing internal integrations, onboarding teammates, and deploying to infrastructure another team owns. You weren’t just running apps; you were building platforms on top of Aspire. That helped set the direction for our next major release.
That’s what “ready for primetime” means to me: a foundation you can bet on for real enterprise apps, without outgrowing the experience that makes even the simplest Aspirified apps a delight.
Aspire 17 gives you more of the levers to build that platform, from a shared starting point for your team to a clearer view of a growing app and more deployment options. Here are the changes I think you’ll be most excited about. The complete inventory, migration notes, and breaking changes live in the aspire.dev What’s New.
Aspire as the paved path for your teamAs Aspire has matured, we’ve heard more stories from you about using it to build your company’s developer platform. That planning moment in June got us thinking bigger, too: what would it take to make Aspire the paved path for any new service inside Microsoft?
We figured that if we could make it work for Microsoft in a way anyone could extend, that would be a pretty good proof point. Microsoft-specific integrations can stay internal and be maintained by the teams driving them, but the extensibility they need belongs in Aspire so you can build on it.
That starts when a new teammate joins or your team spins up a service. Your team should be able to find your service starter, internal hosting integrations, and the agent skills that explain your infrastructure without piecing them together from a wiki.
In 17, your platform team can define those defaults in one Git-backed configuration source. Point the CLI at it with ASPIRE_INIT_SOURCE_URL; aspire new or aspire init offers the source and asks before adopting it. Your templates become discoverable, aspire add can find your internal feeds, and aspire agent init configures your team’s skills.
You can also try templates directly from Git, without publishing a template package. Here’s a real repository to explore:
aspire new --template-repository https://github.com/Azure/aspire-templates
Fork a starter, add your own hosting integrations, and make your platform’s conventions available through the same commands developers already use. My favorite part is that developers still choose what to trust: templates and plugins can run code. These are shared defaults, not enforced policy. See team configuration sources for setup and refresh details.
Your app, at a glanceThe dashboard is often the first thing that gets people hooked on Aspire. It’s been a core part of the experience from day one, and we always want to keep that immediate sense of “I can see my app!” as your apps get bigger.
When we surveyed experienced Aspire users about the dashboard, the most common first action after aspire run was wonderfully straightforward: wait for things to turn green. Opening an endpoint was another top activity. Before digging through telemetry, you want to know whether your app is ready and get to the part you’re working on.
A lot of that detailed investigation is work that many of us now delegate to coding agents. In the survey, just under half of you told us that you “often” or “always” used agents to investigate your logs and traces. But the dashboard is about the human moments: visual feedback, opening your app, showing a peer how it fits together, or onboarding a teammate. When I open it myself, I want quick context and a clear next action.
The redesign opens with the familiar resource table, putting status and endpoint links up front. Selecting a resource brings its details and telemetry together. Select All resources for a Summary of health and live activity, without piecing it together across pages.
For bigger apps, Aspire 17 brings tagging. Here’s the TestShop playground app, with its catalog, checkout, and storefront resources grouped alongside their related parameters:

Define shared tags in your AppHost by team or subsystem. For example, give a checkout service and its parameter the same tag:
WithTags is experimental in 17. You can also add personal tags on the fly in the dashboard, without editing the AppHost. Shared tags give everyone a starting point; your own tags let you organize the app around the work you’re doing. Choose Group resources to group by tags, type, or state.
Then pick the resources you care about once. In TestShop, I’ve selected frontend and both catalogservice replicas in Structured logs. Capture is paused on completed HTTP requests so the shared trace links stand out. Ctrl-click (Command-click on macOS) to add a resource, then flip to Traces or Metrics and the selection comes with you. No rebuilding your filters on every tab.

Here’s that workflow in motion, from tags and parameters to a distributed trace and metrics:
Switch to Graph to see how your services and dependencies connect, or pin the metrics you check most. Read the full tour in Explore the dashboard.
Give us your feedback
Try the new dashboard with your app and tell us how it feels. If the new experience isn’t ready for you yet, switch back in Settings by choosing Previous dashboard under Dashboard experience.
Welcome to our newest AppHost language, GoGo AppHosts have been promoted from experimental to preview in 17. The experimental flag is gone, and Go shows up in aspire new and aspire init.
aspire new aspire-go-starter -n aspire-app -o aspire-app
cd aspire-app
aspire run
In the Go starter, you get a Go API and a React frontend, with Redis available as an option. The AppHost is Go too, with typed APIs generated for your integrations. It builds on the same hosting integrations as C# and TypeScript AppHosts: the Aspire Type System exposes those APIs through an idiomatic Go SDK rather than a separate implementation of each integration. My favorite part is the debugger: with the Go extension and Delve in VS Code, hit F5 and you’re stepping through your AppHost.
You need Go 1.26 or later, and you start the AppHost with aspire run instead of go run ., because the CLI supplies the connection the generated SDK talks to. Learn more in Get started with the Go AppHost.
.NET apps, simplifiedWhen your AppHost references every .NET service as a project dependency, building the AppHost means traversing that whole graph before you get to the dashboard. In 17, the new .NET project model separates those jobs: start the AppHost and dashboard, then let Aspire coordinate the service builds before launching them.
The stable Aspire.Hosting.Dotnet integration lets you add a .NET project by path, without a ProjectReference from your AppHost. Services can live in different solutions, and a Go or TypeScript AppHost can add them through the same model:
It supports SDK-style C#, F#, and Visual Basic projects, plus file-based C# apps. Aspire builds compatible projects together, and the resource’s Rebuild action picks up source changes without restarting the AppHost.
For a walkthrough, watch my .NET Conf session with Damian Edwards, where Damian shows the upgrade in action.
Plan your migration
Aspire 17’s .NET AppHosts and library packages require .NET 10 or later. Apps you orchestrate can still target earlier .NET versions if they don’t use those packages.AddProject, AddCSharpApp, and Aspire.AppHost.Sdk are obsolete but still work. Moving to AddDotnetProject changes resource types and build ownership; aspire run --watch doesn’t support it yet. Read the migration guide and 17 breaking changes before you upgrade.
Keep your agent current, without the repo clutterIf you’ve run aspire agent init before, you’ve probably seen Aspire skill files appear in your repo. That got agents started, but left you wondering which copies to commit, which were current, and whether a local copy was overriding newer guidance.
Aspire moves with the agent ecosystem: first MCP, then skills and canvases, and now a plugin that brings the pieces together. Your harness can install and update Aspire guidance through its own plugin or skill system, rather than leaving you to refresh Markdown files in every repo. Updates no longer have to wait for a new Aspire CLI bundle.
Aspire guidance is available for agent harnesses including Codex, Claude Code, GitHub Copilot, and OpenCode. Update it through your harness’s plugin or skill workflow; the exact controls depend on the harness. See the agent setup guide for your harness, and review any old local skills that could override the new guidance.
In Copilot environments, the plugin also brings canvases for environment checks, AppHost resources, and reviewing an Aspireify wiring proposal.
With the guidance in place, I want my agent working from the app I actually have running. Give it a map: aspire describe can now print the running app’s resource graph as Mermaid:
aspire describe --format mermaid
I’ve been loving this one. Paste the diagram into a PR description or a slide deck to show what’s actually running, instead of the one someone drew last year. It also gives an agent a compact view of your topology. The dashboard can export it too.
Once you’ve narrowed down the failure, attach to a running .NET or Go resource from the Aspire view in VS Code without restarting it under the debugger. Copilot can request the same through aspire_resource_debug, with your confirmation before attaching.
See aspire agent init, aspire describe, and the Aspire VS Code extension for the details.
Ship it to KubernetesIf your platform team already owns the cluster, Aspire should be able to deploy your app without taking over that infrastructure.
Aspire.Hosting.Kubernetes ships as a stable package in 17 and targets existing Kubernetes clusters, locally or in any cloud. Generate Helm charts for your deployment pipeline, or let aspire deploy apply them using your current Kubernetes context.
Aspire.Hosting.Azure.Kubernetes, also stable in 17, adds Azure Kubernetes Service (AKS) provisioning and Azure resource integration. See the Kubernetes and AKS deployment guides for setup.
Point your AppHost at a pre-provisioned AKS cluster with the existing-resource APIs. Aspire deploys your workloads without reconfiguring the cluster’s settings. The existing-cluster guide covers the prerequisites.
Each environment also gets its own secrets. With API_KEY already set in your shell, store a Staging value and deploy with it:
aspire secret set Parameters:api_key --envvar API_KEY --environment Staging
aspire deploy --environment Staging
Secret commands still default to Development. Omit the value to enter it at a masked prompt instead of putting it in your shell history.
AKS control-plane tier
For clusters that Aspire creates, the default AKS control-plane tier changes from Free to Standard, which has a cluster-management charge. Upgrading the package alone doesn’t change an existing cluster, but redeploying its infrastructure can. Set the tier explicitly if you want to stay on Free, and review the cluster identity migration before redeploying an existing Aspire-managed cluster. Secret storage also moves to~/.aspire/secrets; see secret migration if your tools edit user-secrets files directly.Start with Deploy to AKS and deployment environments.
Grab bagA few more things I’m excited about in 17:
aspire tray start puts them in your menu bar or desktop tray, instead of making you hunt through terminals.*.dev.localhost, and Codespaces forwarding.
Thank you, friends of AspireI am SO proud of this team and community. Look at what you’ve helped us build! Over the past six months, 94 contributors have had 1,715 pull requests merged into the Aspire repo.
Every issue, PR, docs fix, and app you’ve shared has pushed Aspire further than we could have taken it on our own. Thank you for the honest feedback, the wild ideas, and for betting on this thing with us. You built this release with us, and I can’t wait to see what you build on it next. 
Get Aspire 17Update the CLI, your apps, and your agent setup:
aspire update --self
aspire update
aspire agent init
Then run your app, select a couple of resources in the new dashboard, and follow a request across them. If you’re a Go developer, try aspire new aspire-go-starter. If you’re building a platform for your team, try sharing a starter and your hosting integrations through a config source.
New to Aspire? Install the CLI with your package manager of choice.
Share feedback on GitHub, join us on Discord, follow @aspiredotdev on X, find us on BlueSky, or subscribe on YouTube.
Happy Aspirifying! 
PS: If you’re wondering what happened to 14, 15, and 16, ask yourself: were those numbers really ready for primetime? 
The post Aspire 17 is ready for primetime appeared first on Aspire Blog.
Yesterday I had the pleasure of presenting “Bending Aspire to Your Will” at VISUG XL, where we celebrated 20 years of the Visual Studio User Group (VISUG). It was a great occasion to share ideas with the developer community, get inspired and see a lot of familiar faces again.
I started with a quick tour of Aspire 'as-is': its AppHost, dashboard, resources and observability features. Then, using an API-testing scenario as an example, I showed how to shape and customize Aspire around a developer’s workflow:
The takeaway: Aspire isn’t just a way to run your application locally. Its resource model and extension points let you build tooling that fits the way your team and your AI agents work.
The presentation can be found here: presentations/Visug XL - 2026 at main · wullemsb/presentations
And if you want to take a look at the final demo, have a look here: wullemsb/aspire-samples
It contains a customized version of the Aspire Webshop example demonstrating all the features above and more.
Thanks to everyone who joined the session, and congratulations to VISUG on 20 years!
Explore the new SQL Formatter in SSMS 22. Learn how to format T-SQL code for better readability and efficiency.
The post SQL Formatter in SSMS 22 appeared first on MSSQLTips.com.