Why milestone 13.0?

[KalleOlaviNiemitalo]

.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?

[KennethHoff]

I was wondering this myself. Not only was the milestone changed, but the default branding is updated as well: #11651

__ (Before release) => 8.x => 9.x => 13.x is an unusual versioning scheme.

My initial guess was that they changed from following .NET versions to following C# versions, but surely it would be version 14.x if that was the case.

[KalleOlaviNiemitalo]

Does Microsoft have some other product with which they might be aligning version numbers? Presumably not Windows 11, Visual Studio Code 1.105, nor C# Dev Kit 1.71.4… perhaps instead something related to Azure or AI?

[BobH-Official]

I believe its should be : dotnet 10 - visual studio 18(2026) - C# 14 - F# 10.0 - Visual Basic 17.13 And Aspire 13. non of them matches. 😂

[Varorbc]

@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?

[davidfowl]

We will reveal this when the time is right. Just know that it is not a joke, it is real.

[KalleOlaviNiemitalo]

Unmarked answer because Aspire 13.0 was released and https://aspire.dev/whats-new/aspire-13/ does not say why it is version 13 rather than 10.

[davidfowl]

13 is bigger than 10 and less than 14 and is a prime number. The versioning scheme signifies a break away from .NET versioning and a direction change in the product to be evergreen (latest version is what matters) and going polyglot.

[BobH-Official]

so the next version will be 17?

by meaning "a break away from .NET versioning" and "be evergreen", does it means it will be force to use non-LTS dotnet SDK? even non-LTS Java/NodeJS, really?

Will good to hear about going polgyglot, any plans?

[davidfowl]

by meaning "a break away from .NET versioning" and "be evergreen", does it means it will be force to use non-LTS dotnet SDK? even non-LTS Java/NodeJS, really?

Aspire currently is multi-faceted so its complex but the idea is to help customers stop thinking about how aspire versions and .NET version align, because they don't. Aspire 13 supports .NET 8, 9 and 10. The apphost .NET version has no influence on what version the applications use. This versioning is the first step to signal that to users, we will decouple this more and more as time goes by.

Will good to hear about going polgyglot, any plans?

All over the roadmap #10644 and the website https://aspire.dev/

[niltor]

@davidfowl

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!

[rwxzig]

What happened to the Blazor, now I see that aspire.dev is released with Astro and under Microsoft?
What is exactly happening?

[KalleOlaviNiemitalo]

I'd prefer that you post that as a separate question (perhaps at https://github.com/microsoft/aspire.dev/discussions), as it is not highly related to the version numbering.