Aspire v13 - Support for .net9

[ianmcd0]

A few notes about our current environment.

• Using .NET 9 for all projects (cannot upgrade for ~8 months due to internal constraints).
• Using Aspire 9.5 (sort of!).
• At this stage, we have it established in 10 microservices primarily for integration, resilience and telemetry features. Each of the microservices is owned by a different team and different repo. The teams don't place any importance on Aspire as yet.
• We have a POC solution, that uses submodules to bring in the 10 repos and additional Apphost project to do orchestration.
• We hope to foster interest in Aspire, but to be successful we need it to be their flexible friend.

Current Issue:

• Aspire 13 requires .NET 10, so upgrading Aspire is blocked until we move to .NET 10.
• Aspire integrations (RabbitMQ, Oracle EF Core, etc.) pin specific NuGet versions.
• This prevents us from using the latest versions of these libraries, which is critical for security patches and vulnerability mitigation.
• We want to stay aligned with Aspire’s “official” versions for stability, but this conflicts with our need for up-to-date dependencies.

If I could upgrade to .net10 I would but that is not something I have control over. The latest Microsoft.Extension libraries (v10) support .net9, would have hoped for similar from Aspire.

Given our POC stage I feel it is time to back away from it, but want to confirm. Will v9.5 be the final Aspire version to support .net9?

[davidfowl]

Aspire 13 requires .NET 10, so upgrading Aspire is blocked until we move to .NET 10.

The aspire CLI requires .NET 10 SDK, Aspire 13 still works with .NET 8 and 9.

Aspire integrations (RabbitMQ, Oracle EF Core, etc.) pin specific NuGet versions.

Minimum versions yes, what are you running into?

We want to stay aligned with Aspire’s “official” versions for stability, but this conflicts with our need for up-to-date dependencies.

It shouldn't stop you from updating.

Given our POC stage I feel it is time to back away from it, but want to confirm. Will v9.5 be the final Aspire version to support .net9?

See the above.

cc @eerhardt @joperezr

[eerhardt]

RabbitMQ

Note that there was a major breaking change in the RabbitMQ.Client library between v6 and v7. Aspire 13 offers 2 libraries depending on which one you need:

• https://www.nuget.org/packages/Aspire.Hosting.RabbitMQ => references RabbitMQ.Client v7.x
• https://www.nuget.org/packages/Aspire.RabbitMQ.Client.v6 => references RabbitMQ.Client v6.x (but doesn't allow v7 since it won't load on that version).

Oracle EF Core

This integration hasn't received any updates lately. It would be great if someone familiar with Oracle could step in and update it for EF 9 and EF 10.

[joperezr]

As shared above by @davidfowl, the expectation is that you should be able to continue to target .NET 9 with Aspire 13, as Aspire will continue to target and support all current .NET supported versions, which as of now means .NET 8, 9 and 10. Note that this is the same for .NET tooling, meaning that if you want to use the aspire CLI, you should still be able to update your Tooling (SDK, Visual Studio, etc) to 10.0 versions without needing to re-target your application to .NET 10, as it is totally supported to use dotnet 10 tooling to target older TFMs. In fact, the general guidance to customers is to try to stay up-to-date in terms of tooling as we continue to improve them, no matter which TFM you decide to target.

[ianmcd0]

I'm confused now about the problems I was facing last week! I had tried upgrading our solutions to v13 but faced difficulties, can't recall the message but incompatibility with net9.0 was mentioned. Then the documentation showed an update of the target framework to net10.0 and jumped to the wrong conclusion. After reading your advice, I tried again - this time it was painless.

Thanks for taking the time to respond all. I'm enjoying the road trip with Aspire, always excited to see what is coming next!