migrating-data-edm-to-odata Skill
Migrates the obsolete Microsoft.Data.Edm (OData v1–v3 EDM types) to Microsoft.OData.Edm for OData v4. Use ONLY when Microsoft.Data.Edm has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.Data.Edm is still supported. Published by microsoft in upgrade-agent-plugins.
What is migrating-data-edm-to-odata Skill?
Migrates the obsolete Microsoft.Data.Edm (OData v1–v3 EDM types) to Microsoft.OData.Edm for OData v4. Use ONLY when Microsoft.Data.Edm has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.Data.Edm is still supported. Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use migrating-data-edm-to-odata Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-data-edm-to-odata/SKILL.md
What it does
Migrates the obsolete Microsoft.Data.Edm (OData v1–v3 EDM types) to Microsoft.OData.Edm for OData v4. Use ONLY when Microsoft.Data.Edm has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.Data.Edm is still supported.
Skill instructions
Microsoft.Data.Edm to Microsoft.OData.Edm Migration Overview Migrate projects from the OData v1–v3 EDM library (Microsoft.Data.Edm) to the OData v4 EDM library (Microsoft.OData.Edm). The primary change is a namespace rename, but several model interfaces gained new members and some types were renamed to align with the OData v4 specification. Related skills: migrating-data-odata-to-odata-core, migrating-data-services-client Package Reference Changes Old Reference (Remove) xml <PackageReference Include="Microsoft.Data.Edm" Version="5." / New Reference (Add) xml <PackageReference Include="Microsoft.OData.Edm" Version="{latest-stable-version}" / Use tools or NuGet to find the latest stable version. Workflow Migration Progress: - [ ] Step 1: Detect Microsoft.Data.Edm usage - [ ] Step 2: Update package references - [ ] Step 3: Update namespace declarations - [ ] Step 4: Handle API differences - [ ] Step 5: Update validation calls - [ ] Step 6: Build and verify Step 1: Detect Microsoft.Data.Ed
Explore related resources
Frequently asked questions
What is migrating-data-edm-to-odata?
migrating-data-edm-to-odata is a open-source AI agent skill with Copy skill directory. Migrates the obsolete Microsoft.Data.Edm (OData v1–v3 EDM types) to Microsoft.OData.Edm for OData v4.
Who is migrating-data-edm-to-odata best for?
migrating-data-edm-to-odata is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install migrating-data-edm-to-odata?
Install or run migrating-data-edm-to-odata using Copy skill directory. Check migrating-data-edm-to-odata for the latest setup command.
Is migrating-data-edm-to-odata actively maintained?
migrating-data-edm-to-odata may need a closer maintenance check before production use.
Auto-fetched from GitHub.
