Master C#, .NET, EF Core, frontend, databases, and architecture.
No spam. Unsubscribe anytime.
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.
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.
