dotnet-entity-framework6

Migrate EF6 to EF Core by first auditing feature usage, then moving one bounded context at a time using parallel coexistence or module-by-module approaches. Validate each slice with integration tests against the real database provider, not InMemory.

Keep EF6 when the application is stable, relies on EDMX designer models, complex stored procedure mappings, or ObjectContext APIs. Consider EF Core when targeting .NET 6+, needing cross-platform deployment, or requiring features like compiled queries and interceptors.

Yes, EF6 can run on modern .NET, which lets you upgrade the runtime without porting the ORM. This path suits applications where the runtime upgrade is needed but an EF Core migration is too risky.

EF6 features without direct EF Core equivalents include the EDMX designer, ObjectContext API, automatic migrations, and Entity SQL. Identify these early in the audit because they significantly raise migration cost.

EF Core has different LINQ translation behavior, cascade delete defaults, and shadow property handling than EF6. Write characterization tests before migration and compare generated SQL for critical queries to catch regressions.