Support for ASP.NET Core 5 & Versioned API Explorer

[gingters]

Hello,

are there plans to make the Api versioning compatible with .NET 5?

The current ASP.NET Core 5 web api templates include swagger, which in turn needs the versioned API explorer, but that package won't install in a .NET 5 RC1 web api project.

[commonsensesoftware]

Plans - yes, but there's nothing coming anytime "soon". I run this project largely alone and I don't have capacity to chase pre-releases. I've been particularly booked up these past months. I'm currently working on burning down the existing set of issues. Once have got that down to a reasonable size, I'll start looking at support for .NET 5.0. The ASP.NET team usually reaches out if they expect to have visible breaking changes (but not always). I suspect the main work will be just adding an additional build target. I don't know what the exact planned date for .NET 5.0 is yet, but I know it will be in November.

Thanks for patience.

[gingters]

For your info:

I did a very quick check (replaced target framework netcoreapp3.1 by net5.0), hotpatched the compilation errors that resulted from the nullable types (if x == null throw...) and checked the swagger sample.

Result was: It worked with all version documents as I would expect that.

So, aside from the nullable type issues that should be resolved properly and not just shortcutted as I did for the very brief test it is indeed adding the target framework for net5.0 in addition to netcoreapp3.1 and that should be it.

[commonsensesoftware]

That's good to know. I've finally caught up with the backlog and I've knocked down the pile of OData issues. I'll start taking a look at this. There's about a month left before RTW, so there's a reasonable chance I'll have this ready by then. I'll almost certainly have to multi-target to support those not ready to push forward to .NET 5.0 just yet. That should be the only level of complexity to deal with.

I also noticed that the ASP.NET team is planning on releasing in-box scaffolding for OpenAPI/Swagger with Swashbuckle. I may have to reach out and see if they are also interested in any versioning scaffolding as well. :)

I'll report back when I have package version ready.

[commonsensesoftware]

5.0.0-preview.1 is now available. I expect the official packages to land within a day of .NET 5.0. I don't currently have any other planned changes to the core libraries. I'm hope to have release parity with OData, but I won't let that hold this up. Thanks.

[PMExtra]

I'm looking forward for this.
.NET 5.0 stable is released several weeks. I need ControllerNameAttribute and ActionNameAttribute but Microsoft.AspNetCore.Mvc.Versioning still does not support .NET 5.0 .

[WeihanLi]

Is there a plan for 5.0 release date?