azure Serverless like a Superhero with Azure Functions In my most recent Pluralsight course, I spent some time talking about using Swashbuckle to create documentation for ASP.NET Core WebAPI applications. Swashbuckle is the .NET Core implementation of
azure Use a container to show your function swagger One option for enabling the Swagger-UI capabilities is to direct the consumers of the api to http://petstore.swagger.io and have them put the url in the box at
azure Unmasking your swagger with proxies in Azure Functions In my post Testing Azure Functions with Postman and Swagger I showed how to use the API Specification capabilities in Azure Functions and then take the endpoint url and test
azure Testing Azure Functions with Postman and Swagger A new feature (preview) in Azure Functions is API Definition. This feature allows you to use the OpenAPI specification (aka Swagger) to document the functionality of your functions and/or
aspnetcore Don't lose your swagger with dotnet build See GitHub Issue #795 for the details and discussion. One of the undocumented changes of converting from project.json to csproj, was the <DocumentationFile> no longer automatically copied
aspnetcore Documenting ASP.NET Core WebAPI using Swagger When you create a web API, documenting its capabilities for the consuming developers can be a task if you take it on manually. Swagger gives you the ability as the
