dotnet-ef-migrations

EF Core migrations let you evolve your database schema from C# code. Generate a migration with `dotnet ef migrations add`, review the generated migration file, then apply it with `dotnet ef database update`. This keeps your database in sync with your DbContext models across development and production environments.

Yes. EF Core generates idempotent SQL scripts that safely run multiple times without errors. Use `dotnet ef migrations script` to create deployment-ready SQL, or bundle migrations with `dotnet ef migrations bundle` for self-contained, repeatable production rollouts without requiring EF Core tooling on the server.

Use the `HasData()` method in migration configurations to insert seed data, or call `migrationBuilder.Sql()` to execute raw SQL commands. This gives you fine-grained control over data population and schema customization during migration execution.

Remove unpushed migrations with `dotnet ef migrations remove`, or revert applied migrations using `dotnet ef database update [previous-migration]`. For conflicts in shared code, coordinate with your team, remove conflicting migrations, and reapply them in the correct order to maintain a linear migration history.

Yes. EF Core migrations support both SQL Server and PostgreSQL through provider packages: `Microsoft.EntityFrameworkCore.SqlServer` for SQL Server and `Npgsql.EntityFrameworkCore.PostgreSQL` for PostgreSQL. Configure your DbContext with the appropriate provider to generate database-specific migration scripts.

Install the required NuGet packages: `Microsoft.EntityFrameworkCore.Design` for tooling, plus your database provider package. Configure your DbContext in your application, then use the `dotnet ef` CLI commands. The Design package enables migration scaffolding and script generation.