The document discusses the implementation of Swagger in an ASP.NET Core 2.0 application using the Onion architecture, presented by Abhinav Jha on March 14, 2018. Swagger, part of the OpenAPI specification, provides tools for API documentation, testing, and deployment, making it easier for developers and non-developers to understand and interact with web APIs. The document also outlines how to install and configure the Swashbuckle.AspNetCore package to generate dynamic API documentation.

1. Asp.Net Core API
With Swagger
Implemented Swagger with Asp.Net Core 2.0 application with
onion architecture.
Presented By:
Abhinav Jha
14th March 2018

2. What is swagger. Why we need it?
Swagger is the world’s largest framework of API developer tools for the OpenAPI
Specification(OAS), enabling development across the entire API lifecycle, from design
and documentation, to test and deployment.
When consuming a Web API, understanding its various methods can be challenging for
a developer.
Swagger, also known as Open API, solves the problem of generating useful
documentation and help pages for Web APIs.
It provides benefits such as interactive documentation, client SDK generation, and API
discoverability.
I am using Swashbuckle.AspNetCore for my .Net Core 2.0 api to create its
documentation dynamically.

3. What do we need?
From the Package Manager Console window:
~ Install-Package Swashbuckle.AspNetCore
From the Manage NuGet Packages dialog:
● Right-click your project in Solution Explorer > Manage NuGet Packages.
● Set the Package source to "nuget.org".
● Enter "Swashbuckle.AspNetCore" in the search box.
● Select the "Swashbuckle.AspNetCore" package from the Browse tab and click
Install.

4. Implementation
Configuring Swagger

5. Configure Middleware
Register the Swagger generator, defining one or more Swagger documents
using Swashbuckle.AspNetCore.Swagger;

6. Enabling Swagger

7. Execution
Running Application.

8. Swagger UI

9. Swagger UI API Documentation

10. Swagger UI Model Declaration

11. Advantages Of Swagger
● It's comprehensible for developers and non-developers. Product managers,
partners, and even potential clients can have input into the design of your API,
because they can see it clearly mapped out in this friendly UI.
● It's human readable and machine readable. This means that not only can this
be shared with your team internally, but the same documentation can be used to
automate API-dependent processes.
● It's easily adjustable. This makes it great for testing and debugging API
problems.

12. References
To dig into the power of swagger refer these links for upcoming features.
Official Site:
https://swagger.io/
Swashbuckle.AspNetCore:
https://github.com/domaindrivendev/Swashbuckle.AspNetCore
Microsoft Documentation:
https://docs.microsoft.com/en-us/aspnet/core/tutorials/getting-started-with-
swashbuckle?tabs=visual-studio%2Cvisual-studio-xml