WebAPI Versioning

You've already got clients accessing your RESTful API and now you want to provide new features. You need versioning.

Topics include:
- ASP.NET Versioning
- Swagger
- Adding, removing and modifying API features
- Reusing existing features in a new C# controller
- Reporting available APIs to the client
- Defaulting to the existing API

[CodingTutorialsAreGo]

Do your API vary much, or once published are they stable? Let me know.
And if you liked the video, click the 👍.

[gazells]

Clearly explained and engaging, thanks so much!

[gazells]

If v2 of a controller action takes in a model with extra/modified properties, do I create a new model? And should I create a new repository class to handle v2 controller actions?

[VindicatorMorty]

Interested in the next parts because those are the different ones. I am just curious about the decision to go straight to 2.0. Basically the summaryfortitle endpoint is a new Feature. That would mean for every Feature you raise the major Version. What if you Just add a property to an existing Model. That could be handled tolerant (by ignoring it) within the api consuming Client. Imo that would be a raise of the minor Version of the model itself.

[foudilbenouci]

Couldn t you make v2 controller inherit from v1 controller and only add the new action ?

[foudilbenouci]

A controller cant be dependency injected ?