* Update to current version
* cleanup AddSwaggerGen snippets
* moving OpenApiInfo to proper location
* powerapps and flow version note 2.0 example
* annotations update
* annotations edit
* edit pass
* fix note
* update line number
Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>
* Update version of Swashbuckle.AspNetCore to 5.0.0
* update 2 other version numbers
Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>
* Adds Missing "using" statements
Fixes#13701
References same file as the InfoClassNamespace. I PR'd that file as well. /tutorials/web-api-help-pages-using-swagger/samples/2.0/TodoApi.Swashbuckle/Startup2.cs
* Added CS for missing namespaces
* Replaced relative path with absolute path
For navigating to CS file with missing namespaces.
* Update NSwag URLs to current GitHub location
* Add solution for web-api-help-pages-using-swagger projects
* Bump NSwag and Swashbuckle package versions
- current and next versions
- will need to bump versions again to pick up latest Microsoft-provided features
* React to latest NSwag and Swashbuckle versions
- lots of renames and type changes (especially `string` -> `Uri`) in NSwag
- Swashbuckle now relies on Microsoft.OpenApi.Models
- disable OpenAPI doc generation in other .NET Core 2.0 project
* Remove unused namespaces
- NSwag and Swashbuckle now use common `Startup` namespaces such as Microsoft.AspNetCore.Builder
nit: sort `using`s
* remove extra comma
* Move solution file into samples folder
* Minor tweaks (#12980)
You should import the Swashbuckle.AspNetCore.Swagger namespace _before_ adding the Swagger generator to the services collection or you get a red squiggly.
I spent a day or more researching this so that I could use Swagger-UI in my ASP.NET Core API which is used with a reverse-proxy and virtual directory. In the end found Swagger-UI requires relative URLs to start with a period. Related to https://github.com/swagger-api/swagger-ui/issues/4107
Hoping this documentation note will help others.
When creating a new PR, please do the following and delete this template text:
* Reference the issue number if there is one:
Fixes #Issue_Number
> The "Fixes #nnn" syntax in the PR description causes
> GitHub to automatically close the issue when this PR is merged.
* overview
* whats new to end
* fix migration node
* split fundamentals, move to end
* glob & loc, get started
* security node name
* security section
* azure, client-side, host
* several more sections
* redistribute tutorials
* proofread fixes
* move how to download section
* index files delete and redirect
* fix errors
* reorder some nodes
* scott feedback, flatten main tutorials node
* fix missed feedback items + other issues
* unflatten tutorials node
* move 'how to download'
* more tutorials node tweaks
* standardize view sample links
* db --> DB
* fix build error
* remove link from a parent node
* streamline node names
* xref links
* typos
* typo
* typos and revert some xref links
* scott feedback
* scott feedback
* feedback
* change node name
* safe storage-->protect