-
Notifications
You must be signed in to change notification settings - Fork 347
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
Should EntityFrameworkTasks
use dotnet-ef.exe
rather than dotnet.exe
#1213
Comments
Feel free to send a PR. |
@matkoch This would be a breaking change to anyone who had not installed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usage Information
NUKE Execution Engine version 7.0.2 (Windows,.NETCoreApp,Version=v6.0)
Description
EntityFrameworkTasks
expectsdotnet-ef
to be added as adotnet tool
instead of allowing it to be added as a nuget package reference vianuke :add-package dotnet-ef
Reproduction Steps
Given the following task:
Running
nuke EF
throws the following exceptionThis is expected as I haven't added
dotnet-ef
to the project.So I now run
But running
nuke EF
throws the same exceptionExpected Behavior
I would expect that all that was required to use
EntityFrameworkTasks
would be to install thedotnet-ef
nuget package vianuke :add-package dotnet-ef
Actual Behavior
The actual behaviour is that you are required to install
dotnet-ef
as a dotnet tool viaRegression?
No response
Known Workarounds
The issue stems from the tool using
dotnet.exe
as the tool executable rather thandotnet-ef.exe
.We could resolve
dotnet-ef
usingBut we would then have to change the tasks to not prefix the commands with
ef
. For exampleef database drop
would need to change todatabase drop
Could you help with a pull-request?
Yes
The text was updated successfully, but these errors were encountered: