Replies: 3 comments 1 reply
-
I would be open to that change. I am hoping to ship a light 4.0 release in the next week based on @mattbrailsford changes that focus around Sqlite. I'm trying to re-think how I manage this project going forward, and I think I have been to hesitant to make breaking changes and it slows progress. |
Beta Was this translation helpful? Give feedback.
-
@jzabroski I would suggest to think about all experience, create a new project and move gradually stuff from the old one starting with the most used database. You don't have to write a new code, just to place puzzles (classes) you already have. IMHO. |
Beta Was this translation helpful? Give feedback.
-
Any news on this? I have the same problem.. want to use FluentMigrator in a Blazor WASM project but it is not possible right now because of all the database implementations that ships with it. |
Beta Was this translation helpful? Give feedback.
-
I am not sure if it's a big deal. I am using Sqlite in my project. Also I use dependency injection (as I found it's kind of mandatory to execute migration scripts).
So I added
FluentMigrator
andFluentMigrator.Runner.Sqlite
nugets. Then I have found that there is no way to use it without actually addingFluentMigrator.Runner
which contains all database implementations I don't need.From the other side why do we need
FluentMigrator.Runner.Sqlite
then if you have to addFluentMigrator.Runner
anyway?The question is: should we move
AddFluentMigratorCore()
andIMigrationRunner
toFluenMigrator.Runner.Core
project? So I can simply useFluentMigrator.Runner.Sqlite
?Beta Was this translation helpful? Give feedback.
All reactions