migrating-webapi-odata

Automate migration of OData services from ASP.NET Web API to ASP.NET Core OData.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-webapi-odata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-webapi-odata
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-webapi-odata
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-webapi-odata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the migration of legacy ASP.NET Web API OData services to the newer ASP.NET Core OData framework, simplifying the transition and ensuring compatibility with modern application requirements.

Core Features & Use Cases

  • Automatic Migration: Facilitates the conversion of OData services from ASP.NET Web API to ASP.NET Core OData.
  • Version Compatibility: Designed for use when the legacy OData library is deprecated or flagged as obsolete.
  • Use Case: Ideal for developers looking to upgrade their applications to utilize the latest features and improvements of ASP.NET Core OData.

Quick Start

Run the 'migrating-webapi-odata' skill to begin the migration process for your OData services.

Frequently Asked Questions about migrating-webapi-odata

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

FAQPage Schema
How do I migrate OData services from ASP.NET Web API to ASP.NET Core?

Migrating OData services to ASP.NET Core requires updating project references, registering OData in dependency injection, migrating controllers, and updating EDM model configuration to ensure compatibility with modern application requirements.

What is the process for updating EDM model configuration when migrating to ASP.NET Core OData?

Updating EDM model configuration involves adapting your existing OData Entity Data Model to the newer ASP.NET Core OData framework. The migration provides a step-by-step guide to correctly register and configure the updated EDM.

When do I need to migrate my legacy ASP.NET Web API OData services?

You need to migrate your legacy OData services when the existing ASP.NET Web API OData library is deprecated, flagged as obsolete, or when upgrading to utilize the latest features and improvements of ASP.NET Core OData.

Do I need prior knowledge of both frameworks to automate ASP.NET Core OData migration?

Yes, automating the OData migration requires existing knowledge of both ASP.NET Web API and ASP.NET Core frameworks, as well as underlying OData concepts, to successfully update project references and register dependencies.

What is the best way to register OData in dependency injection during an ASP.NET Core migration?

The best way to register OData in dependency injection is to follow the automated step-by-step migration guide, which systematically configures OData services within the ASP.NET Core dependency injection container.