Future Proof with ASP.NET Core API Versioning
summary
Shows how to version ASP.NET Core APIs using the open-source Asp.Versioning library, with concrete code paths: install the NuGet, call addApiVersioning, and decorate controllers with [ApiVersion]. Demonstrates four version readers—URL segment, query string, API-version header, and media-type—how to combine them, how to report supported/deprecated versions via response headers, and how to publish sunset policies. Recommends semantic versioning, header-first strategy, and defaulting unspecified requests to 1.0 for brownfield migrations.
AI-written summary · about
chapters (21)
- 0:00Future-proofing APIs
- 1:09Why versioning matters
- 3:14API versioning basics
- 5:45ASP.NET Core versioning libraries
- 8:16Four versioning strategies
- 13:36Configuring versioning in startup
- 17:50Versioning controllers and actions
- 23:34Version-neutral endpoints
- 25:23Convention-based versioning
- 28:16Accessing API version in code
- 30:04Handling missing versions
- 33:16Default API versions
- 35:52Multiple version readers
- 36:14Advertising API versions
- 37:35OPTIONS for versions
- 38:37Deprecating API versions
- 41:09Versioning best practices
- 44:43Communicating with consumers
- 47:08Next steps for versioning
- 48:54Q&A: Unchanged endpoints
- 53:32Q&A: Upgrade paths
related talks
16mASP.NET Core 2.2
51mAPI Versioning In Spring Framework 7
50mAPI Versioning for REST: In Real Life, How Do We Do It?
51mBuilding Web APIs with ASP.NET Core
01h 03mASP.NET Core 1: What has changed for MVC and Web API developers?
58mMinimal APIs in ASP NET 6 0
01h 18mProfessional Web APIs using ASP.NET Core 2.1
25mHow to Approach Retroactive API Versioning