Versioning APIs with ASP NET Core

Announcing .NET Core 3.0: aka.ms/dotnetcore3
Building an API with ASP.NET MVC in .NET Core is only half the job. If your API is going to live more than one release cycle, you are going to need to version it. In this talk by Shawn Wildermuth, we'll show you how easy it is now to version APIs using functionality built into ASP.NET Core.

[@rameshbhaskar]

Amazing and crystal clear.

[@LivingTheDream21]

Definitely was not sleeping. Great job Shawn! Very clean and concise. Explained very thoroughly, where I did not have any questions, yet concise.

[@rahulmathew8713]

Thank you so much for this presentation. Now that's what I call a masterclass content.

[@DedicatedManagers]

Great job Shawn... I’ve been watching a lot of the .Net Conf videos and some presenters are very confusing; on the other hand I found your presentation to be very clear and easy to understand. So thank you!

[@Marlonsgarcia16391]

Great video thanks a lot Shawn it was really clear and clean

[@ValerianPereira]

This was an excellent demo for API versioning. Though I am a beginner at dotnet core, it was a super smooth experience, where I spun a sample app in minutes to test this bit. Thanks Shawn. I would like to follow more videos from you specifically to get proficient with dotnetcore.

[@rupinderjitsinghbatra]

Very clean and clear.

[@ME-dg5np]

Very good man! 👍

[@123spaceinvaders]

nice presentation!! thanks

[@veevek]

Take away: Don't read the license agreement, Just install it. That's the way it works. 100% agree. lol

[@ericb.9777]

Even if the presentation is good, i must say that i am not fond of mixing multiple version of an API in the same source code. I prefer to consider each API version as a dedidated product with its own lifecycle and release chain.

[@plamenyovchev]

What would be the best approach if want to notify my client apps that there is a new API version(update).
I can think of 3 possible scenarios.
1. Polling the server every X minutes to check the current version and to compare it with the locally cached one
2. Use SignalR and when new client connects to the server then notify him for the current API version so the client will be able to make it's comparisons
3. Use header versioning which then the client should send that header with each http request, then if there is a mismatch between the versions the server will return BadRequest then the client should get the supported api version from the response headers and update the local cache and reload the app
Whaat would be you suggestion ?

[@BOOFSIDEPINS]

yes

[@mzuhry4263]

hi sir. could i get your code?