NSwag.AspNetCore instead of Swashbuckle.AspNetCore

[Varorbc]

Swashbuckle.AspNetCore is no longer activity, and NSwag.AspNetCore instead of Swashbuckle.AspNetCore

aspnetcore/src/ProjectTemplates/Web.ProjectTemplates/WebApi-CSharp.csproj.in

Line 22 in 76d2fda

<PackageReference Include="Swashbuckle.AspNetCore" Version="${SwashbuckleAspNetCoreVersion}" Condition="'$(EnableOpenAPI)' == 'True'" />

[davidfowl]

What do you mean Swashbuckle.AspNetCore it's no longer active?

[Varorbc]

Swashbuckle.AspNetCore is no longer activity and does not support Aot, while NSwag.AspNetCore already supports Aot, so I recommend NSwag.AspNetCore instead of Swashbuckle.AspNetCore

[davidfowl]

NSwag.AspNetCore supports AOT? Can you point me to this support?

[Varorbc]

Sorry, not fully supported yet

[marinasundstrom]

Personally, I prefer NSwag, but that is a choice based on feature set.

The C# client generator (NSwag) works best with NSwag's OpenAPI document.

I have been following the NSwag repository, and it is pretty much a one man operation by @RicoSuter. A lot of issues and PRs that never have been closed. So hard to keep track of what is happening. BTW. If so, can the community assist him in some way?

A major difference between the libraries is that Swashbuckle uses System.Text.Json, while the NSwag toolchain is built on Newtonsoft Json.

Overall, both libraries might be considered stable, so there are no changes unless there are serious issues.

I'm a proponent of making this a choice.

But as it is now, it is pretty easy switching out Swashbuckle for NSwag.AspNetCore. And the ASP.NET Core documentation mentions them both:

• Get started with Swashbuckle and ASP.NET Core
• Get started with NSwag and ASP.NET Core

The purpose of having Swashbuckle in the template is just to have something to start with.