skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

migrating-data-edm-to-odata

Migrate OData v1–v3 EDM types to OData v4 in .NET projects.

19|2|Updated May 13, 2026
Search Tags:#data migration#OData#API change#EDM migration#namespace update
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-data-edm-to-odata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrating-data-edm-to-odata
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-data-edm-to-odata
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-data-edm-to-odata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need to migrate applications from the obsolete Microsoft.Data.Edm library to the more modern Microsoft.OData.Edm library for OData v4 compatibility.

Core Features & Use Cases

  • Namespace Update: Automatically updates namespace references from Microsoft.Data.Edm to Microsoft.OData.Edm.
  • API Difference Handling: Guides through API changes and updates between OData v1–v3 and v4.
  • Validation API Update: Provides instructions for updating validation calls to the new API.
  • Quick Migration Workflow: Offers a step-by-step workflow for a smooth migration process.

Quick Start

Use the migrating-data-edm-to-odata skill to update your project's package references from Microsoft.Data.Edm to Microsoft.OData.Edm.

Frequently Asked Questions about migrating-data-edm-to-odata

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

FAQPage Schema
How do I migrate from Microsoft.Data.Edm to Microsoft.OData.Edm in .NET?▼

Migrate Microsoft.Data.Edm to Microsoft.OData.Edm by updating package references and applying namespace changes to transition your .NET project to the OData v4 EDM library.

What API changes occur when upgrading to OData v4 EDM types?▼

Upgrading to OData v4 EDM types involves API difference handling and validation API updates, requiring namespace reference changes from Microsoft.Data.Edm to Microsoft.OData.Edm.

When do I need to replace the deprecated Microsoft.Data.Edm library?▼

You need to replace the deprecated Microsoft.Data.Edm library when upgrading applications from OData v1–v3 to OData v4 compatibility, ensuring your EDM types align with the modern Microsoft.OData.Edm library.

Does this OData v4 migration workflow update validation API calls automatically?▼

The OData v4 migration workflow provides instructions for updating validation API calls to the new API structure, ensuring your validation logic aligns with the Microsoft.OData.Edm library.

What are the limitations of migrating EDM types to OData v4?▼

Migrating EDM types to OData v4 requires understanding of namespace changes and API updates between OData v1–v3 and v4, meaning manual code adjustments may be needed beyond automated namespace updates.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
19

migrating-system-spatial

Migrate spatial data types from System.Spatial to Microsoft.Spatial for OData v4.

Official
Advanced
microsoftmicrosoft
19

migrating-data-services-client

Migrate Microsoft.Data.Services.Client code to Microsoft.OData.Client for OData v4.

Official
Intermediate
kashiashkashiash
6

xaf-web-api

Expose XAF business objects as OData v4 REST endpoints with JWT authentication.

Community
Advanced
microsoftmicrosoft
19

migrating-webapi-odata

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

Official
Advanced