Today, a lot of people end up deploying all of their migrations with their app. If they're applying those migrations as part of deployment, they just sit there taking up space.
We could introduce a new kind of project just for migrations. After creating the project, calling dotnet ef migrations add would add new migrations to this separate project keeping them out of your app. The result of building this project could even be a migrations bundle (see #19693).
Today, a lot of people end up deploying all of their migrations with their app. If they're applying those migrations as part of deployment, they just sit there taking up space.
We could introduce a new kind of project just for migrations. After creating the project, calling
dotnet ef migrations addwould add new migrations to this separate project keeping them out of your app. The result of building this project could even be a migrations bundle (see #19693).