entity-framework6

# Entity Framework 6 ## Trigger On - working in an EF6 codebase on .NET Framework or modern .NET - deciding whether to keep EF6, move to modern .NET runtime, or port to EF Core - reviewing EDMX, code-first, or legacy ASP.NET/WPF/WinForms data access - planning a data layer migration strategy ## Workflow 1. **Audit current EF6 usage** before planning any migration. Identify which features the codebase depends on: ```csharp // Common EF6-specific patterns to inventory: // - EDMX designer models (check for *.edmx files) // - ObjectContext vs DbContext usage // - Lazy loading with virtual navigation properties // - Database.SqlQuery<T>() for raw SQL // - Stored procedure mappings in model // - Spatial types (DbGeography, DbGeometry) ``` 2. **Decide runtime vs ORM migration separately:** | Path | When to use | |------|-------------| | Keep EF6 on .NET Framework | Legacy app with no runtime pressure | | EF6 on modern .NET | Runtime upgrade needed, ORM migration too risky | | EF6 → EF Core | Clean data layer, no EDMX, minimal stored-procedure mapping | 3. **For maintenance work** — keep EF6 stable: - use repository + unit of work patterns to isolate data access (see [references/patterns.md](references/patterns.md)) - prefer `DbContext` over `ObjectContext` for new code - use `AsNoTracking()` for read-only queries - configure concurrency tokens with `[ConcurrencyCheck]` or `IsRowVersion()` 4. **For migration work** — validat...