The issue I'm having is that it appears that no comparison against the target database is made when I "Add-Migration," and the Up/Down methods are empty.
I begin by focusing on various environments. When I update-database and it just targets one database, my development database, the migration changes function as intended.
The Up/Down methods are never empty when I try to add migration for that specific environment after changing the connection string to target a different database, another development box on a different server, etc.
I attempted to target an update-database to the second development box to roll back modifications made during a previous migration, but nothing changed.
Is there anything in particular I should do when moving code-first changes between environments?
Instead of adding a new migration, you must command EF to execute all the existing ones. Attempt defining the migrations' source and target:
Update-Database -SourceMigration: $InitialDatabase -TargetMigration: AddPostAbstract
By adding -Script to the command, you can also create a script that you can run on the other database.
You could role up your migrations if you have a lot of them by eliminating them and performing a brand-new add-migration.