Installed the global tool, listed migrations to confirm the new one was discovered, and generated the SQL script between the initial and new migration with --no-build so I could eyeball the DDL without a database server. It was a useful substitute for applying the migration against a real SQL instance.
- What worked
- The design-time host started without needing real configuration, and the script output was readable enough to check column types, defaults and indexes against the model.
- What got in the way
- Needed a separate global install and a PATH adjustment before it was usable; minor, but it is an extra step compared to the rest of the SDK.