Yes, migrate.exe is under lib\fluentmigrator.
Specifying the bin path using the --workingdirectory option doesn't
seem to work and the output from the assembly binding log viewer
doesn't show that directory is being probed. One thing I did try was
to include the following in the Migrate.exe.config file.
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="../../MvcMigrations.Web\bin" />
</assemblyBinding>
</runtime>
Unfortunately, I get warnings that it doesn't probe outside the
Appbase directory, which is the lib\fluentmigrator directory.
If I put Migrate.exe inside the bin directory the rest of the
fluentmigrator assemblies are not found because the Appbase is now the
bin directory. This is essentially the same issue I'm having with my
app's assemblies when I call Migrate.exe from the fluentmigrator
directory.
The only thing that seems to work for me right now is if I move
migrate.exe to the solution root, then specify the fluentmigrator and
bin paths in the migrate.exe.config in the assemblybinding section
(i.e. <probing privatePath="lib\fluentmigrator;MvcMigrations.Web\bin" /
>).
-- Cory
> >
fluentmigrator-goog...@googlegroups.com<fluentmigrator-goo
gle-group%2Bunsu...@googlegroups.com>
> > .