You have just successfully released your first Web API built in ASP.NET Core. Other applications are consuming the Web API and all is good. Then a newer version of your APIs needs to be build and you find that you have to deal with both new and old consumers. Versioning and backward compatibility becomes necessary all of a sudden.
This session will show you how to add versioning support to your ASP.NET Core Web APIs. We will look at implementing multiple versions, version routing, versioning strategies, version discovery and adding documentation from Swagger. You are going to learn what it takes to evolve your Web APIs from version 1.0 until deprecation, but also how clients can consume the right version of APIs.
Short: Learn all about versioning your Web APIs in ASP.NET Core. You will see when multiple versions are necessary and how to take care of hosting different versions, routing requests and using conventions, documentation and properly use version formats for long-term support of your web-based API.
Alex is an application development enthusiast since the late nineties and works as an architect, lead developer and mentor at large enterprises and small companies. He spends his time teaching other developers the details of the Microsoft development platform and frameworks, and coaches architects to design and build modern distributed applications at cloud scale. He has received the Microsoft Most Valuable Professional award for Visual Studio and Development Technologies 15 times. In his spare time Alex likes to participate in all kinds of sport, and loves playing and programming new and retro video games.