What’s happening with v9?

[adrianhall]

Hey folks,

I wanted to give you an update on what’s happening with v9.

Firstly, we are code complete for all existing code. That means you can build the library, upgrade your projects to .NET 9 and EF Core 9 and they will “just work”.

There is one little bit of code left to write - support for the .NET 9 OpenApi library. I’ve got two services in test right now. The sample server works fantastically - all the appropriate operations and parameters get produced; there is just a small issue where I need to write a schema transformer for the nextLink - it’s listed as a URI in the generated OpenApi document but it’s a string since we only transmit a query string. However, my new test service doesn’t work at all - the OpenApi service doesn’t find the controllers unless you add an ApiExplorerSetttings(Ignore = false) attribute to every single controller, and the parameters and models that are produced are not valid at all. I’ve engaged with the team within Microsoft that works on this feature so hopefully we’ll get some progress on this in the near future. Once I’ve got the reliable production of the OpenApi document, I can start to work on the schema transformer that is necessary and then move towards release.

After that, it’s mostly documentation and samples work. I need to upgrade all the samples to .NET 9 (which can be done outside of the release cadence) and I’m going to switch the doc set from Hugo to Mkdocs for purely aesthetic reasons (I like the read the docs template and Hugo doesn’t have one. I don’t want to write one). I also want to do some significant work on the doc set - bring in my blog series as a getting started guide, work on some better tutorials, and also have a tutorial set for the client.

Assuming I can get the OpenApi problem sorted in the next week, I’m still looking good for an end of February release.