A few months ago I started working on a project where we use Fluent Migrator. Everything works fine and the project has quite a few migrations running without any problem. Broadly speaking, it works almost the same as EF migrations, with a few differences.
The thing is, today I started a new project and added the reference to the Fluent Migrator package to start using it. When I ran the migrations everything seemed fine (no errors), but it didn’t find any of the migrations I had defined in the migrations assembly.
After going round in circles looking for the problem, I realized that the Fluent Migrator version in the new project was 1.4. Searching a bit, I found an issue describing exactly what was happening to me, but it didn’t give the solution. Pulling on that thread, I also realized that the “migrate.exe” I was running was the one from Fluent Migrator Tools 1.3, because I had its path added to the PATH.
After removing it from the PATH and using the “migrate.exe” from version 1.4, everything worked fine.