Note: not recommended solution. but quick fix in some cases.
For me, dbo._MigrationHistory
in production database missed migration records during publish process, but development database had all migration records.
If you are sure that production db has same-and-newest schema compared to dev db, copying all migration records to production db could resolve the issue.
You can do with VisualStudio solely.
dbo._MigrationHistory
table in source(in my case dev db) database > Click "Data Comparison..." menu.Note that, again, it is not recommended in complex and serious project. Use this only you have problem during ASP.Net or EntityFramework learning.