aspnet-api-versioning VS ASP.NET Boilerplate

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.

https://aspnetboilerplate.com/ (por si alguien le interesa)

This is pretty similar

Aspnet boilerplate has great documentation and handles multi tenant. Good design patterns and supports several front-end frameworks. https://aspnetboilerplate.com/

DotNetBoilerplate might suit your needs. They also have a more advanced commercial offering

Hi beautiful people of learnprogramming. I’m a Junior-Developer and I‘m having a hard time learning the backend-part of the Framework I been using for the past months. We use ASP.NET for the backend and Angular for the front. The angular part gets slowly better, the backend I‘m a complete noob. We use http://aspnetboilerplate.com and the learning curve is so high.

Evo ja trenutno radim za klijenta koji ima vise projekata i koriste ASP.netZero koji se placa a bazira se na AspNetBolerplejtu. Ti bojlerplejtovi su odmah spremi za rad sa Angularom, Vue ili Reactom za front.

Hands down ABP. Download and follow the tutorials, you’ll get a great education out of it. It’s multi tenant and the documentation is excellent. ASP.net: https://aspnetboilerplate.com

ABP was an acronym for "ASP.NET Boilerplate". However, it is the name of the previous generation: https://aspnetboilerplate.com/ ABP.IO is the next generation of the ASP.NET Boilerplate framework and we no longer use the long name, because the "Boilerplate" word is misleading (they think it is just a startup template, but actually a complete framework & platform).

Alright, so I'm using an https://aspnetboilerplate.com/ template with Angular and it's awesome. Basic Angular app that is responsive, lots of out of the box functionality to play with. Here's a screenshot of the structure: https://imgur.com/a/WOPOKj1