dotnet-entity-framework6

Guide EF6 application maintenance and migration to EF Core.

466|35|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-entity-framework6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-entity-framework6
Source: https://github.com/managedcode/dotnet-skills/tree/main/skills/dotnet-entity-framework6
Command: npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-entity-framework6

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps .NET developers manage existing Entity Framework 6 (EF6) codebases and provides clear guidance on modernizing or migrating to EF Core, preventing common pitfalls and ensuring a smooth transition.

Core Features & Use Cases

  • EF6 Maintenance: Offers best practices for keeping EF6 applications stable and performant.
  • Migration Guidance: Outlines strategies and decision frameworks for moving from EF6 to EF Core or modern .NET runtimes.
  • Use Case: You have a legacy ASP.NET application using EF6 and need to decide whether to refactor to EF Core or simply upgrade the .NET runtime. This Skill provides a decision tree and step-by-step advice.

Quick Start

Use the dotnet-entity-framework6 skill to get guidance on migrating an EF6 application to EF Core.

Frequently Asked Questions about dotnet-entity-framework6

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

FAQPage Schema
How do I migrate an EF6 application to EF Core?

To migrate an EF6 application to EF Core, you should separate runtime upgrades from ORM upgrades and use a decision framework to validate migration slices. This approach ensures a smooth transition by addressing legacy data access patterns incrementally rather than rewriting everything at once.

What is the best way to maintain a legacy Entity Framework 6 codebase?

Maintaining a legacy Entity Framework 6 codebase involves applying best practices to keep applications stable and performant. You should review existing EDMX or code-first patterns and seek realistic maintenance advice to manage technical debt without forcing an immediate framework upgrade.

Should I upgrade the .NET runtime or refactor to EF Core first?

You should separate runtime upgrades from ORM upgrades when modernizing EF6. Upgrading the .NET runtime first provides immediate benefits while allowing you to use a structured decision tree to plan your Entity Framework Core migration independently.

How do I handle EDMX legacy data access patterns when moving to modern .NET?

Handling EDMX legacy data access patterns during a modern .NET move requires reviewing the existing models and applying validated migration slices. This process ensures you can safely transition away from visual designers without breaking core data access logic.

Does this EF6 guidance work for both code-first and EDMX approaches?

Yes, this EF6 guidance covers scenarios involving both code-first and EDMX approaches. It provides specific reviews and maintenance advice tailored to your application's existing data access patterns to ensure confident modernization.