Start Debugging

Tag: openapi

16 posts · Page 2 of 2

2026-06-16 migration swashbuckle openapi

Migrate from Swashbuckle to the built-in OpenAPI generator in .NET 11

A step-by-step migration from Swashbuckle.AspNetCore to Microsoft.AspNetCore.OpenApi in .NET 11: swapping AddSwaggerGen for AddOpenApi, converting operation, schema, and document filters to transformers, keeping a UI, and the Microsoft.OpenApi v2 breaking changes that bite.

2026-06-08 csharp dotnet dotnet-11

How to expose OpenAPI without Swashbuckle in ASP.NET Core 11

Swashbuckle is gone from the ASP.NET Core templates. Here is how to generate and serve an OpenAPI document in .NET 11 with the built-in Microsoft.AspNetCore.OpenApi package: AddOpenApi, MapOpenApi, transformers, multiple documents, build-time generation, and a UI on top.

2026-05-24 dotnet-11 aspnetcore openapi

ASP.NET Core in .NET 11 Preview 4 Teaches OpenAPI About the HTTP QUERY Method

.NET 11 Preview 4 makes ASP.NET Core OpenAPI generation recognize HTTP QUERY as a first-class operation in OpenAPI 3.2, with a graceful fallback for 3.0 and 3.1 documents.

2026-04-28 dotnet-10 aspnetcore openapi

Asp.Versioning 10.0 finally plays nicely with built-in OpenAPI in .NET 10

Asp.Versioning 10.0 is the first release that targets .NET 10 and the new Microsoft.AspNetCore.OpenApi pipeline. Sander ten Brinke's April 23 walkthrough shows how to register one OpenAPI document per API version with WithDocumentPerVersion().

2026-04-28 aspnetcore openapi swagger

How to add OpenAPI authentication flows to Swagger UI in .NET 11

In .NET 11 the OpenAPI document is generated by Microsoft.AspNetCore.OpenApi and Swagger UI is no longer in the template. Here is how to wire Bearer, OAuth2 with PKCE, and OpenID Connect so the Authorize button actually works.

2026-04-24 dotnet dotnet-11 csharp

How to Generate Strongly Typed Client Code from an OpenAPI Spec in .NET 11

Use Kiota, Microsoft's official OpenAPI code generator, to produce a fluent, strongly typed C# client from any OpenAPI spec. Step-by-step: install, generate, wire into ASP.NET Core DI, and handle authentication.