Most projects push every row through HasData and end up with fake data in migrations or empty production tables. Here is when to use HasData, UseSeeding and your own seeder class - all three in one EF Core 10 app.
Every new screen adds another repository method with its own copy of the same Where, Include and OrderBy. The Specification pattern gets the interface down to two methods that never change again - with exactly the same SQL.
Claude can write C# but has no idea what's in your database until you give it a way to ask. Build your first MCP server in .NET 10 with EF Core and SQL Server, expose three tools, and use it from Claude Desktop and MCP Inspector.
Two real production scenarios on a 1-million-row catalog - a tiered pricing promotion and a live CSV feed import - with numbers measured on camera: where a hand-rolled EF Core loop is fine, and where BulkUpdate, BulkMerge, and BulkSynchronize from Entity Framework Extensions turn 51 seconds into 12.
Your multi-tenant EF Core app might be leaking one customer's data into another customer's response right now - here's how EF Core 10's named global query filters fix that for good.
Build a self-contained EF Core migration bundle in GitHub Actions, apply it to Azure SQL as a dedicated deploy step, then ship the API to App Service - schema and code moving together, with a smoke test at the end.
Calling Database.Migrate() on startup is the demo answer, not the production one. How to actually ship schema changes - idempotent SQL scripts, migration bundles, a least-privilege migration login, and reviewing what EF generated.
Your app is making 1501 SQL queries per request - and the code looks completely fine. Learn how to identify and fix the N+1 problem and Cartesian explosion in EF Core.
Record who changed what and when, automatically, by overriding SaveChangesAsync and walking the EF Core change tracker - with old/new values as JSON, sensitive fields stripped, and the current user pulled from the request.
EF Core 10 ships first-class LeftJoin and RightJoin operators, named query filters you can disable individually, complex types mapped to JSON, and native vector search for RAG - a tour of what actually changes day to day.
EF Core can map a C# class hierarchy to the database three different ways - one shared table, a table per class with joins, or a table per concrete type. Here is how each one looks on disk and which to pick.
Build one generic repository that handles CRUD for every entity, extend it per-aggregate for the queries that do not fit, and wire it into a Clean Architecture solution with MediatR and PostgreSQL.
Two requests read the same bank account balance and both write back - one update silently disappears. Fix it with an EF Core rowversion, a caught DbUpdateConcurrencyException, and a bounded retry.
Updating or deleting many rows by loading them, changing them in a loop, and calling SaveChanges is the slow path. ExecuteUpdate and ExecuteDelete send one SQL statement and skip the change tracker entirely.
A DELETE statement is forever. Soft delete in EF Core using a global query filter, why cascade deletes need special handling, and how to still query the "deleted" rows when you actually need them.
Every EF Core relationship bug traces back to a misunderstood foreign key or a missing configuration. One-to-one, one-to-many, and many-to-many mapped explicitly with the Fluent API, and where EF Core's conventions quietly get it wrong.
Returning every row and letting the client slice it up doesn't survive real data volume. Server-side pagination in a .NET 8 Minimal API - Skip/Take, pagination metadata in a response header, and a React Pagination component wired to it.
A full CRUD build from an empty folder to a working movies app - a CQRS-shaped .NET 8 Minimal API backed by SQLite, and a React + TypeScript client that talks to it. The architecture choices that hold up as the app grows past a toy example.
Schedule recurring work in .NET with Quartz.NET - cron triggers, a hosted service, dependency injection into jobs, and a real EF Core cleanup task that trims an ever-growing log table.