Merge pull request #32442 from dotnet/Rick-Anderson-patch-1
Update getting-started-with-swashbuckle.mdpull/32444/head
commit
5ae30b25e8
|
@ -344,7 +344,7 @@ In the `Startup.Configure` method, enable the middleware for serving the generat
|
|||
> [!NOTE]
|
||||
> Swashbuckle relies on MVC's <xref:Microsoft.AspNetCore.Mvc.ApiExplorer> to discover the routes and endpoints. If the project calls <xref:Microsoft.Extensions.DependencyInjection.MvcServiceCollectionExtensions.AddMvc%2A>, routes and endpoints are discovered automatically. When calling <xref:Microsoft.Extensions.DependencyInjection.MvcCoreServiceCollectionExtensions.AddMvcCore%2A>, the <xref:Microsoft.Extensions.DependencyInjection.MvcApiExplorerMvcCoreBuilderExtensions.AddApiExplorer%2A> method must be explicitly called. For more information, see [Swashbuckle, ApiExplorer, and Routing](https://github.com/domaindrivendev/Swashbuckle.AspNetCore#swashbuckle-apiexplorer-and-routing).
|
||||
|
||||
The preceding `UseSwaggerUI` method call enables an embedded version of the Swagger UI tool. This depends on
|
||||
In development, the preceding `UseSwaggerUI` method call enables an embedded version of the Swagger UI tool. This depends on
|
||||
the [Static File Middleware](xref:fundamentals/static-files). If targeting .NET Framework or .NET Core 1.x, add the [Microsoft.AspNetCore.StaticFiles](https://www.nuget.org/packages/Microsoft.AspNetCore.StaticFiles/) NuGet package to the project.
|
||||
|
||||
Launch the app, and navigate to `http://localhost:<port>/swagger/v1/swagger.json`. The generated document describing the endpoints appears as shown in [OpenAPI specification (openapi.json)](xref:tutorials/web-api-help-pages-using-swagger#openapi-specification-openapijson).
|
||||
|
|
Loading…
Reference in New Issue