.net 8 support

[julianlumets]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

No response

Describe the solution you'd like

Please make the package work with .net 8

Additional context

No response

[commonsensesoftware]

Development is in the works. There were a number of changes in the building tooling that had to be resolved. Things are close to being ready. If all goes well, the release should come by week's end. 🤞🏽

[cfauchere]

will it take care of the stackoverflow?

[commonsensesoftware]

@cfauchere Which stackoverflow are you referring to?

[cfauchere]

@cfauchere Which stackoverflow are you referring to?

the MapVersionedODataRoutes method leads to stackoverflow after bumping to net8.0

[commonsensesoftware]

@cfauchere I'm not sure the exact context here, but MapVersionedODataRoutes is dead and no longer exists. That was removed from the libraries 2 years ago starting with the official OData 8.0 support. There is no such open issue, nor has it ever been reported for the old Microsoft.AspNetCore.OData.Versioning library up to 5.1.0, which only targets .NET Core 3.1 because OData didn't have .NET 5.0 release at the time.

I can't speak for OData's versioning policy or strategy, but it does not align to the .NET version releases. Although it's rare to encounter issues, there is no guarantee that a library that does not target the runtime version will necessarily work. If you target ASP.NET Core 8.0 on .NET 8, then you need a version of such a library targeting .NET 8 to be sure it will work. API Versioning always releases a version that is in alignment with ASP.NET Core and the version of .NET that it builds against. That effort is currently underway. That is what this issue is about.

I can't force people to follow that rule. You can try to make things work with other versions. It might work. It might work and you may never have issues. It is not, however, guaranteed. If that happens, it's unsupported. I have seen issues occur in the wild. Be advised. There be 🐉🐉🐉.

I get the impression you are attempting a rather large update that includes moving to OData 8.x and .NET 8.0. I presume you must have been on OData 7.x or performed some other 🧙🏽‍♂️🪄 to make things work. If you have questions about migrating or need help, a new discussion might be more appropriate. OData didn't do us any favors in aligning configuration or extension points, but things are more aligned than they used to be. Regardless, there is a significant difference in the setup between OData 7.x to OData 8.x+. The migration guide doesn't cover this situation because the only official version of API Versioning that supports OData 8.0+ is an entirely new package ID and API. The wiki outlines the setup and differences between OData 8.0 vanilla versus with API Versioning, but not in contrast to the old APIs and OData libraries. I'm happy to discuss further to help you move forward.

[cfauchere]

@commonsensesoftware thanks for the follow up. You're correct that we are currently on OData 7. Let me start a new thread.

here

[commonsensesoftware]

.NET 8 support has been released and published. The NuGet packages should be available momentarily.