🎁 Aspire Roadmap - End of Year Update (December 2025) #13608
Replies: 4 comments 3 replies
-
|
I see .localhost DNS Support is mentioned as shipped in 13.0, is there some document about the detail usage? I tried to search but do not see a detail usage doc. I am expecting to leverage to hide the dynamic port and make it more friendly for local experience. |
Beta Was this translation helpful? Give feedback.
-
|
Hiding dynamic ports is a bit more work than we've done so far (that requires a proxy that owns port 80/443 on the dev's machine). Right now we support |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to do this:
|
Beta Was this translation helpful? Give feedback.
-
|
Is there some public doc about dev.localhost usage? |
Beta Was this translation helpful? Give feedback.
-
|
My favorites:
|
Beta Was this translation helpful? Give feedback.
-
|
What does "Capture and Replay" entail? I'm intrigued |
Beta Was this translation helpful? Give feedback.
-
|
This is a considerable amount of work you guys have achieved in 2025. My company already started using Aspire as the suggested development experience. And we are looking forward to the K8S and AKS deployments to be GA to hopefully incorporate them in our CI/CD. Thank you so much for the great work! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Aspire Roadmap - End of Year Update (December 2025)
Since our 9.5 update, we've shipped two major releases: Aspire 13.0 (November) and Aspire 13.1 (December). This post summarizes our progress against the original roadmap and highlights what's next.
🎉 Major Accomplishments
Aspire 13.0 marked a transformational shift from a .NET-exclusive tool to a full polyglot application platform, elevating Python and JavaScript to first-class status alongside .NET.
Aspire 13.1 introduced comprehensive AI coding agent support through MCP integration and stabilized several key features.
Rebranded to Aspire - We've dropped the ".NET" prefix to reflect our polyglot future. Same great tool, broader vision.
aspire.dev is now live as our official documentation site.
YouTube Channel launched for technical demos and content.
🧑💻 Local Developer Experience
.localhostDNS Support🧪 Testing Experience
📊 Dashboard Enhancements
🛠 Tooling
init,update,run)new,do)aspire mcp init)🌐 Polyglot Support
🤖 AI Workflows
☁ Hosting Integrations
🚀 Deployment
Pipeline & CI/CD:
aspire dopipeline system shipped (13.0)📈 By the Numbers
🔮 Looking Ahead to 2026
Testing remains our largest gap. We're actively experimenting with new testing experiences to make tests behave consistently across local development, CI, and different operating systems. More details next year.
We're also doubling down on onboarding and inner loop experiences. This means continuing work on runtime and tooling acquisition so getting started with Aspire is as frictionless as possible. We're expanding
aspire doto cover more end-to-end scenarios across the full development lifecycle, from environment setup and dependency installation through testing, building, deployment, and environment promotion.Running a subset of Aspire resources is critical for larger projects. We're making good progress with prototypes and hope to ship this in Q1. Multi-repo support continues to be a popular community ask, especially for enterprise teams with distributed codebases. Similarly, dashboard persistence (external storage for telemetry) remains on our radar.
Debugging in containers is one of our most popular asks and we're committed to tackling it in 2026. This requires engineering work in both Visual Studio and VS Code to make the experience as seamless as we want it to be.
Finally, polish. As Aspire grows, we need to smooth out the rough edges when things don't work as expected. Expect better error messages, diagnostics, and an
aspire doctorcommand to help troubleshoot common issues.📚 Resources
Beta Was this translation helpful? Give feedback.
All reactions