Open bricelam opened 4 years ago
We should also consider adding sugar to the product (e.g. (PR #31164)dbContext.Database.HasPendingModelChanges()
) to do this since I've seen a lot of users asking how to over the years.
Some progress was made toward this in PR #14122
We should also double check that the warning surfaces as part of the GenerateEFSQLScripts task and Publish dialog.
We should warn during the following commands when there are pending model changes that can be added to a new migration.
Note, the output of this command could also be used programmatically (via --json) to test if there are any pending model changes(PR #31164)