After .NET 10, do we still have alternatives to openapi?

[niltor]

Previously, we could use Swashbuckle or NSwag to integrate Swagger.
Now, in the official documentation (ASP.NET Core 10), the guidance for these two libraries has been removed, leaving only the official OpenAPI.

Recently, I started migrating my project to .NET 10, and I also started using the official OpenAPI, but I encountered some issues that directly affect my entire workflow.

Since Swagger is a language-agnostic intermediate representation, many teams and tools use it to generate code or import it into API-related tools.

Now, with less than a month until the official release of .NET 10, OpenAPI is not yet production-ready.

So, if the official release cannot fix the problems in time, can we still use Swashbuckle in .NET 10?

Because looking at the Swashbuckle repository, it seems it does not plan to support .NET 10, and its dependencies have not yet switched to Microsoft.OpenAPI 2.0.

This is a significant risk, and I hope the official team takes it seriously.

I doubt whether Microsoft’s internal projects have tested the latest ASP.NET Core OpenAPI.

[martincostello]

You must not have seen this PR: domaindrivendev/Swashbuckle.AspNetCore#3283

[niltor]

Thx, I just read this PR.

Although I'm a bit reluctant, I still have to make a decision right away.

Maybe I should use Swashbuckle in Asp.Net 10.

If possible, could a preview version of Swashbuckle using OpenApi2.0 be released?

Experienced OpenApi2.0 bring destructive changes, then is the official Microsoft AspNetCore. OpenApi unpredictable problem, I spent a lot of energy but don't get the expected result.

Microsoft.AspNetCore.OpenApi should need longer time to improve.

Here, it is suggested that in the subsequent official documentation, the content related to Swashbuckle should continue to be retained so that beginners can have another option.

[martincostello]

See here for details about prerelease builds: domaindrivendev/Swashbuckle.AspNetCore#2349 (comment)