Improve experience for managing migrations

[ajcvickers]

This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.

---

This an "epic" issue for the theme of improving the management of migrations. Specific pieces of work will be tracked by linked issues.

Backlog

• Tools: Support Xamarin/MAUI Projects (currently requires separate .NET Standard class library) #7152
• Migrations: Improve existing database support #2167
• Squash migrations #2174
• Migrations: A command to upgrade snapshots and backing models #18557
• Fully embrace provider-specific migrations #16406
• Consider throwing/warning by default if a migration is used against a different provider than it was generated for #15174
• Wrap SQL for HasServiceTier and HasPerformanceLevel to be ignored when not on Azure #20682
• Adhere to stdout/stderr conventions #22878
• Make it easier to add design-time services #29068
• Enable compositional approach of custom migration functionality #17740
• Construct IDesignTimeDbContextFactory without first discovering all DbContext types #27322
• Improve Migrations Projects #19694
• Running migrations on a project different than startup project - Generic "Unable to create an object of type 'ApplicationDbContext'" error #21106
• dotnet migrations add with --namespace issue #21443
• dotnet-ef database update -1 (down latest migration) #21615
• Tools: Warn when pending model changes #22105

[jerriep]

I am very happy to see some improvements around migrations, especially the squashing of migrations. Thank you for looking into that one!