Why milestone 13.0? #11824
-
|
.NET Aspire 9.5.0 was released last week, but now issues are already being assigned to the 13.0 milestone. And there are no 11.0 or 12.0 milestones. Is there going to be a large jump in version numbers, similar to what Apple did with macOS 26? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 11 replies
-
|
I was wondering this myself. Not only was the milestone changed, but the default branding is updated as well: #11651
My initial guess was that they changed from following .NET versions to following C# versions, but surely it would be version |
Beta Was this translation helpful? Give feedback.
-
|
@davidfowl Hi, there's been some confusion in the community about why Aspire's version number jumped from 9.5 directly to 13. x, skipping versions 10. x, 11. x, and 12.x. Many of us are curious about the reasoning behind this change. Could you please clarify what happened and help resolve this confusion? |
Beta Was this translation helpful? Give feedback.
-
|
The new version is confusing for existing users; I don’t think I need to explain that any further. According to the official documentation, installing Aspire requires a prerequisite: .NET 10. This means Aspire is still tightly linked to specific .NET versions. Since it’s a precondition, regardless of whether the developer is part of the .NET team or not, people naturally associate Aspire with .NET version requirements. As for which .NET versions Aspire supports, this should be specified clearly in the documentation. All in all, these version changes have caused a lot of confusion. On a positive note, I’m really happy to see Aspire making steady progress and playing an increasingly important role among multi-language development teams. I also hope you’ll consider default installation of .NET on Windows first, then gradually expand to Linux, or even macOS. It would be great if you could pass this suggestion along. Now that we have single-file deployment and DNX, .NET is suitable for even more usage scenarios. So, if the .NET SDK could be installed by default on operating systems and kept up-to-date with system updates (which is already partially implemented), the future potential is enormous! Make dotnet great Again! |
Beta Was this translation helpful? Give feedback.
-
|
What happened to the Blazor, now I see that aspire.dev is released with Astro and under Microsoft? |
Beta Was this translation helpful? Give feedback.
We will reveal this when the time is right. Just know that it is not a joke, it is real.