-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrations with dotnet tools #4309
Comments
We are still working that out 😄. It will look very similar to what we have now, but |
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 {
"tools": {
"dotnet-ef": "7.0.0-*"
}
} |
Work is being tracked by #3925 |
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 👍 |
Closing this out now, but feel free to post additional questions (we still follow comments even after the issue is closed 😄) |
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. |
Not yet... |
@julielerman still very much a work in progress, nothing working end-to-end yet |
understood! :) I don't envy you guys right now. |
I tried adding this to project.json:
Running dotnet ef results in this error: Using CLI tools version 1.0.0-beta-001492, OS Platform Windows 10.0.10586 |
How will the migrations command look like with the CLI / dotnet tools - without the commands section in project.json?
The text was updated successfully, but these errors were encountered: