Migrations are a CRITICAL part of using Entity Framework.
The existing Sql Server sample doesn't work with Postgres, takes a considerable amount of work to hack into a state that can work with a different database, and in the end doesn't explain how to set one's one project up to create migrations.
It's highly not-trivial to figure this out.
There are many closed issues on this topic, none of which actually tell a normal developer who isn't on the Aspire team how to create a migration.
This is NOT a solved problem. This is NOT a documented problem.
Please, please, please, write a real end-to-end tutorial that shows how to actually create migrations, not just apply migrations that happen to already exist.
Entity Framework is very important.
Migrations are a CRITICAL part of using Entity Framework.
The existing Sql Server sample doesn't work with Postgres, takes a considerable amount of work to hack into a state that can work with a different database, and in the end doesn't explain how to set one's one project up to create migrations.
It's highly not-trivial to figure this out.
There are many closed issues on this topic, none of which actually tell a normal developer who isn't on the Aspire team how to create a migration.
Examples include:
This is NOT a solved problem. This is NOT a documented problem.
Please, please, please, write a real end-to-end tutorial that shows how to actually create migrations, not just apply migrations that happen to already exist.