Mark Junker

No, not yet. FluentMigrator is built around the concept of migrations working on a connected database. The support for offline SQL generation seems to be an afterthought. It's definitely something...

There is almost nothing we can do here without a huge refactoring. One possible solution might be to create a temporary project/solution which references the project containing the migrations and...

EF stores a snapshot of the database schema in the database itself. This would (theoretically) allow restoring the old DB schema, but not its content. Supporting all edge cases would...

This does indeed seem like a bug where I created a simple service provider in an obsolete [`MigrationContext` constructor](https://github.com/fluentmigrator/fluentmigrator/blob/e82aafa20e6dbe3cefa221303fe23cf8bf59fffd/src/FluentMigrator/Infrastructure/MigrationContext.cs#L55).

I didn't want to open a scope that I had to manage too. There is just one scope - the root one, which should be enough for supporting an obsolete...

`IAssemblyCollection` was too inflexible and did too much in one place. The `IAssemblySource` was a replacement that allowed me to implement the fluent API (see [`.ScanIn`](https://fluentmigrator.github.io/articles/guides/upgrades/guide-3.0-to-3.1.html)) for the configuration of...

We have the following section in the FAQ: https://fluentmigrator.github.io/articles/faq.html#how-can-i-run-migrations-safely-from-multiple-application-servers

I'd like to confirm: 1. Adding the `TestTag` tag to the maintenance migrations (`DbMigrationLockBefore` and `DbMigrationUnlockAfter`) causes the corresponding `Up` function to be called? 2. Do you use transaction per...

Can you please show the code for the FluentMigrator service configuration?

A rollback command doesn't support assemblies and/or tags. This seems like an oversight on my side. The `-p` and `-c` options are connection options and come directly after the `rollback`...