How can I force a 3 month old migration to re-run when I've got 60 or 70 migrations in between and I don't want to/can't do a full rollback?
Apparently supplying the --version parameter of the value that I want it to re-run doesn't work, and neither does just deleting the value from the VersionInfo table (both having been done together also doesn't seem to have any benefit).
Is there a way to have FluentMigrator re-run a single migration from a few months ago? Am I pebkacking the problem?
I'm not sure (try this with careful in in a non production environment), but you can cheat to fluentmigrator altering the versionInfo table.
Add to versionInfo those migrations that you want to NOT execuete
Finally, ensure that the migrations you want to execute ARE NOT in the versionInfo table.
Of course, it would be a good idea to do an export or backup of the versionInfo table prior to any change.