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?