.NET 9 🔥🚀 : ASP.NET Core Web API Versioning

preview_player
Показать описание
In this video we will discussed API versioning and why do we need it?

Support me on Patreon to access the source code:

Let us connect:

Support my work:

Hire Me:

WHO AM I:
I'm Mohamad, a Enterprise Architect working in Manchester, UK. I make videos about web, cloud, desktop and mobile development.

GET IN TOUCH:

#dotnet #api #designpatterns
Рекомендации по теме
Комментарии
Автор

But swagger/openapi doesn't show contracts? How somebody is supposed to use such api?

brandon-
Автор

I prefer ApiVersioning in the route. It keeps the different API versions seperated better. Also I don't really like the look of swagger with the header field. I have seen released API versions with just a subset of endpoint that change, like in you example. Again, using the version in the route then clearly shows you which endpoints have which results. Using a headtag might lead to API users globally substituting the new api version header which will lead to errors. So users still have to change their API usage on and endpoint per endpoint bases, and then having to change the endpoint url is just as much work.
And setting up swagger to use endpoint configuration you get the versions in the top right selectable, which is also nice.

grumpydeveloper
Автор

Tks for vídeo, how make with minimal api and scalar

ItsSalesGabriel
Автор

Nice video, can you please tell me which tool you used for screen recording and editing.

tusharch