Library to document the ASP.NET Web API using the Swagger specification
Latest version: Pre-release 0.6
Swagger.Net will expose any apis the inherit from the ApiController in the new ASP.NET Web API, unless they are flagged with that ApiExplorerSettings(IgnoreApi = true) attribute.
Metadata for the swagger spec is provided by the included DocsController which gives you two new routes.
- root/api/docs - this returns a list of "apis" or "resources" or "controllers" and a path to each to get detailed metadata for that specific controller.
- root/api/docs/{id} where id = controller_name - Detailed metadata for a controller (referenced above).
A Sample.Mvc4WebApi project is included in the repo. The home/index view contains a link to the swaggerui page that uses webpages. (This reduces friction when syncing with the swagger-ui project).
Optionally, you may get the Swagger UI for .NET NuGet package.
Swagger.Net uses a combination of the Web API ApiExplorer class and XML Documentation you write in your /// blocks.
One article that helped me tremendously: [Generating a Web API help page using ApiExplorer] (http://blogs.msdn.com/b/yaohuang1/archive/2012/05/21/asp-net-web-api-generating-a-web-api-help-page-using-apiexplorer.aspx). Thank you!
Swagger.NET conforms to the Swagger specification to support all swagger components including client code gen.
Swagger code generation
Recommened Tags for Documentation in c#
- ASP.NET MVC 4.0
- .NET 4.0
Never attempted. Let us know how it works.
Install the Swagger.Net NuGet package or the Swagger UI for .NET NuGet package. Search for "Swagger" in the package manager or Install-Package Swagger.Net & Install-Package Swagger.Net.UI
-
Enable "XML documentation file" and accept the default value, or specify a custom value (i.e. App_Data\Docs.XML), in the Web API's properties | Build menu (Alt+Enter). If you specify a custom value, you will need to edit the App_Start\SwaggerNet.cs file.
-
Point your browswer at /api/swagger to see the api listing for the Swagger spec or point your instance of Swagger UI (not included, see step 1) at http://YOUR-URL:PORT/api/swagger to expose all of the APIs that you have built. If you have Swagger UI for .NET, point at /swagger.
-
Two new routes are available.
a. /api/swagger returns json listing of all api controllers. (Implemented by SwaggerController)
b. /api/docs/{controller} returns json documentation for given controller. (Implemented by SwaggerActionFilter)
| Example | .net | swagger |
|---|---|---|
| http://www.mydomain.com/ | Endpoint | ResourceListing |
| BlogPosts | Model or Controller | Resource |
| /api/blogposts/{id} | Route (no verb) | Api |
| GET /api/blogposts/{id} | Controller Method | Operation |
| {id} | Method Parameters | Parameters |
Source - .net ApiExplorer object model
Target - SwaggerUI JSON model
I'm hoping you will help me find and/or fix these.
- The version of Swagger UI I have built in the /docs folder DOES NOT WORK in Internet Explorer. :-(
I dropped the Swagger UI directly on the root in a folder called docs, then redirected the index action to /docs. I also edited the index.html file to point it directly at /api/swagger so it can traverse the documentation. The Swagger UI that I installed I got from the Swagger UI GitHub Repo
I have built this library with the lastest versions of everything .NET. (VS 2012, .NET 4.5, etc.) Note: Minimum of .NET 4.0 is required.
Create a fork of Swagger.Net. If you pull down the code, note that the swagger docs are included.
Did you change it? Submit a pull request.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
0.6.1 Return model metadata with api metadata.
0.6.0 Complete refactor using TDD. Added a test project. Removed unused references. Ensure compatibility with VS 2010 with .net 4.0.
0.5.5 Require only .NET 4.0. Fix for duplicate controllers in action filter
0.5.4 Forced the swagger controller to return JSON and removed optional global asax step.
0.5.3 Updated to support the RTM of WebAPI.
0.5.2 Significantly simplified the configuration by using WebActivator in the NuGet package
0.5.1 Created a NuGet package