
Swashbuckle Is Dead. Here's How to Migrate to Scalar in .NET 10.
Why Swashbuckle is no longer the right choice Swashbuckle.AspNetCore was the de facto Swagger UI for .NET for years. Today it has three problems that are hard to work around: Problem Impact No OpenAPI 3.1 support Can't use JSON Schema features ( const , webhooks, $ref siblings) Upstream archived No security patches, no .NET compatibility updates Bypasses native metadata Misses .Produces<T>() , .ProducesProblem() on Minimal APIs Microsoft removed Swashbuckle from the dotnet new webapi template in .NET 9 and replaced it with Microsoft.AspNetCore.OpenApi . That was the official signal. What replaced it Two components, one stack: Microsoft.AspNetCore.OpenApi — first-party document generator, ships with .NET 9+. Hooks directly into the ASP.NET Core endpoint data source. No XML comment parsing, no reflection gymnastics. Generates OpenAPI 3.1 from the metadata you already declared. Scalar.AspNetCore — open-source API reference portal (MIT). Reads any OpenAPI 3.1 document and renders an intera
Continue reading on Dev.to Webdev
Opens in a new tab


