From b910f5ebcd8b708fcfab2cf766edf36ab8d12804 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Tue, 7 Jul 2026 11:29:21 -0400 Subject: [PATCH] docs(claude): note EF migrations --no-build empty-scaffold gotcha `dotnet ef migrations add --no-build` scaffolds off the stale prebuilt DLL and can emit an empty migration; build first and delete the empty Migrations files if it happens (migrations remove needs a live DB). Placed next to the existing EF migrations line in Code Organization. --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index f0cc472d..671198c2 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -221,7 +221,7 @@ Other peers in the `scadaproj` family (see `scadaproj/CLAUDE.md` for details): ` - Per-component configuration via `appsettings.json` sections bound to options classes (Options pattern). - Options classes owned by component projects, not Commons. - Host readiness gating: `/health/ready` endpoint, no traffic until operational. -- EF Core migrations: auto-apply in dev, manual SQL scripts for production. +- EF Core migrations: auto-apply in dev, manual SQL scripts for production. Gotcha: `dotnet ef migrations add … --no-build` scaffolds off the previously-built DLL and can emit an **empty** migration — build first (drop the `--no-build`), and delete the empty `Migrations/` files if it happens (`migrations remove` needs a live DB). - Audit logging absorbed into Configuration Database component (IAuditService). ### Akka.NET Conventions