aspnet-api-versioning VS CleanArchitecture

- 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.

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

Check out the official API versioning Github repository to find out more information.

As others have pointed out, you can use the IHttpContextAccessor. You can see an example implementation in Jason Taylor's Clean Architecture template here: https://github.com/jasontaylordev/CleanArchitecture/blob/main/src/WebUI/Services/CurrentUserService.cs

Not really a good mvc/minimal API project but a good inspiration for me is often this project : CleanArchitecture.

Raytha is built on the popular Clean Architecture template. Anyone who is familiar with the well established CQRS pattern will be able to step right in with a lot of batteries included since the Clean Architecture template is empty. Hope that helps.

Here’s a few: - complex domain driven example using vertical slice - another DDD example - clean architecture template by Jason taylor - clean architecture template by ardalis

This one for CleanArchitecture: https://github.com/jasontaylordev/CleanArchitecture

If you want to try clean architecture, you can check out Steve smith’s repo or Jason Taylor’s repo.

The NUnit example was taken from the Clean Architecture Template, provided by Jason Taylor.