giggio / fluentmigrator.runner.cli Goto Github PK

As described in https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options

Should also add a new migration, a directory and a sql file so we can test.

using the global command

fm --connectionString "Data Source=(local);User ID=***;Password=***;Initial Catalog=***;MultipleActiveResultSets=True;" --provider sqlserver2012

results in the following error

System.NullReferenceException: Object reference not set to an instance of an object.
   at FluentMigrator.Runner.DNX.Program.Main(String[] args)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.Dnx.Runtime.Common.EntryPointExecutor.Execute(Assembly assembly, String[] args, IServiceProvider serviceProvider)
   at Microsoft.Dnx.ApplicationHost.Program.<>c__DisplayClass3_0.<ExecuteMain>b__0()
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

As described in https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options

As described in https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options

Should also create a migration that uses the context to the test project, as described in https://github.com/schambers/fluentmigrator/wiki/ApplicationContext%3A-Passing-parameters-to-Migrations so we can verify.

It would be great if the integrated command line runner could grab the configuration from the Startup class like the EF migration tool does (or rather is supposed to - because it's still not fixed as of beta5).

The EF runner commands have options to specify a DbContext class and the startup project name. From there it's supposed to essentially initialize the Startup class to build the configuration and service dependencies, which in turn should configure the runner.

Some way to point the FM runner to a configured connection string would be ideal.

Isn't the keyword to use this CLI extension clashing with dotnet CLI's own migrate , which migrates from project.json to new msbuild / csproj? What happens when using it with the latest CLIs which will have that keyword?

Documentation for dotnet migrate

Maybe make it similar to how EF does it? dotnet ef migrate ..? So for instance: dotnet fluent migrate ?

As described in https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options

As described on https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options

As described in https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options

As described on: https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options

Should also implement the nested option.
Should also add a migration to a different namespace to the test project so we can verify.

I've just tried this and it doesn't work. The project compiles just fine, but it doesn't seem that the migrations are actually being run. --verbose outputs nothing.

I've tried both dotnet migrate --provider mysql --noConnection --outputFile test.sql and dotnet migrate --provider mysql --connectionString [string]

I've followed the instructions in the top-level README.md, and used the migration in test/ as a sample migration.

Hello,

Is there any plans to add beta7 support anytime soon ? @giggio @lenardg

As described in https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options