skills.rest
AGIBuild
AGIBuildCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-api-versioning

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

10|Updated Jan 28, 2026
Search Tags:#rest api#mvc#asp.net core#api versioning#version management#minimal apis#sunset policy
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-api-versioning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-api-versioning
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-api-versioning
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-api-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of managing multiple versions of HTTP APIs within an ASP.NET Core application, ensuring a smooth transition for consumers as the API evolves.

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 with clear communication via the Sunset HTTP header.
  • Use Case: You have an existing e-commerce API and are releasing a new version with breaking changes. This Skill allows you to run both v1 and v2 of your API concurrently, directing new clients to v2 while providing a clear deprecation path for v1 users.

Quick Start

Configure your ASP.NET Core application 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 manage multiple API versions in an ASP.NET Core application?▼

API versioning in ASP.NET Core is managed using the Asp.Versioning library to run multiple API versions concurrently. This allows you to maintain backward compatibility while releasing breaking changes.

What are the different ways to version REST APIs in ASP.NET Core?▼

REST API versioning in ASP.NET Core supports URL segment, HTTP header, and query string strategies. These approaches route requests to the correct version for both Minimal APIs and MVC controllers.

How do I deprecate old API versions in ASP.NET Core?▼

Old API versions are deprecated using sunset policies that enforce graceful removal. This communicates deprecation schedules to clients via the Sunset HTTP header, providing a clear migration path.

Does ASP.NET Core API versioning work with Minimal APIs and MVC controllers?▼

ASP.NET Core API versioning works with both Minimal APIs and MVC controllers. The Asp.Versioning library provides consistent version management across both programming models.

How do I migrate from the legacy ASP.NET Core API versioning package?▼

Migrating from the legacy API versioning package is supported by the Asp.Versioning library. This transition maintains existing versioning strategies while upgrading to the current package structure.

Related Skills

Explore More Software Engineering Skills→
whopointerwhopointer
1

aspnet-core

Guide ASP.NET Core web development across application models and pipeline composition.

Community
Advanced
teexiiiteexiii

swagger

Serve interactive Swagger UI and raw OpenAPI spec from a TypeScript-based definition.

Community
Intermediate
pluginagentmarketplacepluginagentmarketplace
1

aspnet-core-fundamentals

Guide ASP.NET Core development covering C#, routing, middleware, dependency injection, and testing.

Community
Intermediate
wshaddixwshaddix
71

dotnet-api-versioning

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

Community
Intermediate