Mark Junker
Mark Junker
I (maybe) misread the source code. Does it work when you specify the other tags too?
The problem is, that it cannot create a proper rollback script, because the tool doesn't know the database schema version. There is (in the other external runners) a parameter (`StartVersion`),...
The execution of migrations on published output is something that might be trickier than expected, because you may have a .NET Framework based runner, but want to execute migrations in...
I guess that we have to (somehow) utilize msbuild, probably together with the [C#/VB.NET/F# project system](https://github.com/dotnet/project-system).
This is what we effectively do for the console runner. The problem is the dependencies for the assemblies that contain the migrations.
I think this is what I meant with the following sentence: > The problem with the .NET Core tooling and the new-style package references is, that the package assemblies aren't...
No, that's not supported yet.
Here's what you might want to try: You can create a new class which is derived from PostgresProcessor and override `EnsureConnectionIsOpen()` and `DatabaseType` for a custom identifier. You should then...
I reopened this issue to increase visibility.
The console runner (and `dotnet-fm`) are both out-of-process migration runners. Using `IMigrationRunner` directly is the in-process runner.