aspnet-api-versioning VS cool-webapi

Here is a code example

- The DTOs on the server should generally not change without warning. A deprecation cycle should ideally be in place so consumers can keep up over time and front end development doesn't have to be lock-step with the services the consume. Ideally some period of time between service v1 being deprecated and service v2 being required to allow consumers to react ( in this case, you're the consumer, so be kind to yourself ). Deets: https://github.com/dotnet/aspnet-api-versioning

This API versioning can be parameterized with some options, including the default version or even how the versioning will be done, whether by URL, header or media type. For more details, you can access the official documentation.

https://github.com/dotnet/aspnet-api-versioning/tree/master/samples/aspnetcore/BasicSample/Controllers something like this

Could you not achieve what you want by using ASP.NET API versioning - there's a by namespace example here

A lista completa pode ser vista aqui: https://github.com/microsoft/aspnet-api-versioning/wiki/Version-Format

You don't have to use attributes. You can use conventions. See here.

So far I have added and configured several packages to the cool-webapi project and in the future articles I will add more packages and configuration and the Startup class will become a large class.

You can find the source code for this walkthrough on Github.

Open Startup.cs class and follwing codes:

In the previous article, I wrote about API versioning and how to add Swagger to the sample project with support of API versioning. In this article, I show how to add custom middleware to handle exceptions globally and create a custom response when an error occurred.

Open the cool-webpi project and Install Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer package

Source code for this walkthrough could found on the Github.