TGolla.Swashbuckle.AspNetCore
10.0.0
dotnet add package TGolla.Swashbuckle.AspNetCore --version 10.0.0
NuGet\Install-Package TGolla.Swashbuckle.AspNetCore -Version 10.0.0
<PackageReference Include="TGolla.Swashbuckle.AspNetCore" Version="10.0.0" />
<PackageVersion Include="TGolla.Swashbuckle.AspNetCore" Version="10.0.0" />
<PackageReference Include="TGolla.Swashbuckle.AspNetCore" />
paket add TGolla.Swashbuckle.AspNetCore --version 10.0.0
#r "nuget: TGolla.Swashbuckle.AspNetCore, 10.0.0"
#:package TGolla.Swashbuckle.AspNetCore@10.0.0
#addin nuget:?package=TGolla.Swashbuckle.AspNetCore&version=10.0.0
#tool nuget:?package=TGolla.Swashbuckle.AspNetCore&version=10.0.0
TGolla.Swashbuckle.AspNetCore
This repository contains the following Swashbuckle addons which are part of the NuGet package TGolla.Swashbuckle.AspNetCore.
- Custom Ordering of Controllers
- Adding Authentication/Authorization Information to Swagger API Documentation with Swashbuckle
.NET 10 Upgrade Notes
Starting with .NET 9, ASP.NET Core no longer includes Swagger by default in web API templates. And with .NET 10, Microsoft has doubled down on native OpenAPI support - now generating OpenAPI 3.1 documents out of the box with improved transformer APIs and better tooling. If you’re wondering what changed, whether Swagger is truly dead (spoiler: it’s not), and what the best alternatives are, keep reading to find out! (Ref: ASP.NET Core Dropped Swagger - Here’s What Replaced It in .NET 10 - codewithmukesh)
With the release .NET 10 Microsoft made breaking changes to Microsoft.OpenApi resulting in changes in Swashbuckle document generation. The following is a check list of changes you will need to contline using Swashbuckle along with TGolla.Swashbuckle.AspNetCore and TGolla.AspNetCore.Mvc.Filter.
- Upgrade your Swashbuckle packges to v10.*.
- Upgrade packages TGolla.Swashbuckle.AspNetCore
andTGolla.AspNetCore.Mvc.Filter` to v10.*. - Remove
builder.Services.AddEndpointsApiExplorer();formProgram.cs. in .NET 10 Swashbuckle v10 no longer uses or cooperates with the built‑in Endpoints API Explorer. Leaving it in causes duplicate or conflicting OpenAPI metadata, and Swashbuckle v10 replaces that entire pipeline with its own. - In
Program.cschangeapp.UseSwagger();toapp.MapSwagger();. .NET 8+ introduced a new endpoint‑based middleware model, and Swashbuckle v10 adopted it.UseSwagger()is part of the old middleware pipeline.MapSwagger()is the new endpoint‑based pipeline that aligns with .NET 10’s hosting model.5 - if to have invoking the
AddSecurityDefinitionmethod you also need to indicate which operations that scheme is applicable to. As a result you will need to update anyAddSecurityRequirement()andOperationFilter<AddSecurityRequirement>()implemented byAddSwaggerGen(). Reference Adding Authentication/Authorization Information to Swagger API Documentation with Swashbuckle for complete details.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Swashbuckle.AspNetCore (>= 10.2.1)
- TGolla.AspNetCore.Mvc.Filters (>= 10.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.