dotnet-api-versioning

Implement API versioning strategies for ASP.NET Core with Asp.Versioning.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-api-versioning-rudironsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-api-versioning
Source: https://github.com/rudironsoni/dotnet-agent-harness/tree/main/.rulesync/skills/dotnet-api-versioning
Command: npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-api-versioning-rudironsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing multiple versions of an API within a single .NET application, ensuring backward compatibility and a smooth transition for consumers.

Core Features & Use Cases

  • Multiple Versioning Strategies: Supports URL segment, header, and query string versioning.
  • Sunset Policies: Enables graceful deprecation and removal of older API versions.
  • Use Case: You need to introduce breaking changes to your existing API without disrupting current users. This Skill allows you to create a new version (e.g., /api/v2/) while providing clear guidance and a sunset date for the old version (/api/v1/).

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 ASP.NET Core Minimal APIs?

API versioning in ASP.NET Core Minimal APIs is implemented using the Asp.Versioning.Http package to configure URL segment, header, or query string versioning strategies. This Skill provides guidance on setting up these versioning approaches.

What is the best way to deprecate older REST API versions in a .NET application?

The best way to deprecate older REST API versions is by applying sunset policies using the Asp.Versioning library. This enables graceful deprecation by providing clear guidance and a sunset date for older versions while introducing new ones.

Does the Asp.Versioning library support URL segment, header, and query string versioning?

Yes, the Asp.Versioning library supports URL segment, header, and query string versioning strategies. This Skill covers configuring these multiple versioning approaches for ASP.NET Core applications to ensure backward compatibility.

Can I migrate from legacy API versioning packages to Asp.Versioning in .NET?

Yes, you can migrate from legacy versioning packages to Asp.Versioning. This Skill facilitates migration from legacy packages and ensures compatibility with both Minimal APIs and MVC controllers in ASP.NET Core.

Why do I need API versioning when introducing breaking changes to my REST API?

API versioning is needed to manage multiple API versions within a single .NET application without disrupting current users. It ensures backward compatibility and a smooth transition by allowing you to create a new version while sunsetting the old one.

Can I use API versioning with both MVC controllers and Minimal APIs in ASP.NET Core?

Yes, API versioning can be used with both MVC controllers and Minimal APIs in ASP.NET Core. The Asp.Versioning library ensures compatibility across both approaches, allowing you to apply consistent versioning strategies.