In the second and last part of this series, I'll talk about a frictionless developer experience for versioning .NET APIs and automatically publishing those versions to Azure API Management Services.

API versioning has no “right way” [https://blog.apisyouwonthate.com/api-versioning-has-no-right-way-f3c75457c0b7] and I am fairly convinced that API evolution [https://blog.goodapi.co/api-change-management-2fe5bba32e9b] is usually a better option for both API authors and clients of those APIs. Evolving APIs smoothly without breaking any existing clients and making it easy