skills.rest
wshaddix
wshaddixCOMMUNITY
Explore all skills by this author →
Website𝕏@wshaddixGitHub

dotnet-api-versioning

Implements ASP.NET Core API versioning with URL, header, and query string strategies.

71|10|Updated Feb 11, 2026
Search Tags:#rest api#asp.net core#api versioning#http api#version management#sunset policy
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-api-versioning-wshaddix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-api-versioning
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-api-versioning
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-api-versioning-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of managing different versions of your HTTP APIs, ensuring smooth transitions for consumers and maintainable codebases.

Core Features & Use Cases

  • Multiple Versioning Strategies: Supports URL segment, header, and query string versioning.
  • Sunset Policies: Gracefully deprecate older API versions with clear timelines and migration paths.
  • Use Case: You need to introduce breaking changes to your existing /api/products endpoint. Use this Skill to create a new /api/v2/products endpoint while providing clear instructions and a deprecation timeline for the old /api/v1/products endpoint.

Quick Start

Configure your ASP.NET Core Minimal API project to use URL segment versioning with the Asp.Versioning.Http package.

Frequently Asked Questions about dotnet-api-versioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement API versioning in an ASP.NET Core Minimal API project?▼

API versioning in ASP.NET Core is implemented using the Asp.Versioning library to configure URL segment, query string, or header-based versioning strategies for your HTTP endpoints.

What is the best way to deprecate old REST API versions gracefully?▼

Deprecating old REST API versions gracefully is done by configuring sunset policies that communicate deprecation timelines and migration paths to consumers through HTTP response headers.

Can I use URL segment, header, and query string versioning simultaneously in ASP.NET Core?▼

Yes, the Asp.Versioning library supports configurable URL segment, header, and query string versioning strategies simultaneously within your ASP.NET Core applications.

How do I migrate from legacy API versioning packages to the current Asp.Versioning library?▼

Migrating from legacy API versioning packages is facilitated by the Asp.Versioning library, which provides updated structures to manage HTTP API versions seamlessly in ASP.NET Core.

How are API version details communicated to HTTP API consumers?▼

API version details are communicated to HTTP API consumers through response headers, ensuring clear version identification and providing sunset policy information for deprecated endpoints.

Related Skills

Explore More Software Engineering Skills→
jim60105jim60105
21

csharp-project-init

Initialize C# ASP.NET Core Web API projects with Entity Framework Core and configuration files.

Community
Intermediate
nikblanchetnikblanchet

handle-deprecation-warnings

Identify deprecation warnings and migrate code to recommended APIs.

Community
Basic
burakdmirburakdmir
13

ABP Framework — API Development

Expose ABP application services as REST APIs and generate C# clients.

Community
Advanced
dpieterszdpietersz

Backend API

Design RESTful API endpoints, controllers, and middleware for scalable web services.

Community
Intermediate