Migrations with dotnet tools

[christiannagel]

How will the migrations command look like with the CLI / dotnet tools - without the commands section in project.json?

[rowanmiller]

We are still working that out 😄. It will look very similar to what we have now, but dnx ef will be replaced by something dotnet .... @bricelam is just starting on the implementation now.

[bricelam]

It will be mostly the same. Instead of dnx, you'll type dotnet. To align with the NuGet commands better, we'll probably bring back --startupProject. Your project.json will need to contain the following.

{
  "tools": {
    "dotnet-ef": "7.0.0-*"
  }
}

[bricelam]

Work is being tracked by #3925

[christiannagel]

That's great, so it will be dotnet ef migrations.... This way I don't need to change too much in my book. Also, thanks for the tracking link 👍

[rowanmiller]

Closing this out now, but feel free to post additional questions (we still follow comments even after the issue is closed 😄)

[julielerman]

If using David Fowler's NDC sample https://github.com/davidfowl/dotnetcli-aspnetcore as my starting point, after adding EFCore & EFCore.commands to project.json (restore worked), I am trying to get dotnet ef into the tools section but it's not recognized yet. Is that correct ...not implemented yet or am I doing something wrong (again)? Thanks.

[ErikEJ]

Not yet...

[rowanmiller]

@julielerman still very much a work in progress, nothing working end-to-end yet

[julielerman]

understood! :) I don't envy you guys right now.

[christiannagel]

I tried adding this to project.json:

"tools": {
  "dotnet-ef": "1.0.0-*"
}

Running dotnet ef results in this error:
Failed to initialize CoreCLR, HRESULT: 0x80004005
Am I doing something wrong?

Using CLI tools version 1.0.0-beta-001492, OS Platform Windows 10.0.10586