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
Issues using Microsoft.EntityFrameworkCore.Tools 1.0.0-preview3-final #6855
Comments
The package listed in your |
Ok thanks bricelam, adding that package on tools with the latest version fix the problem now dotnet ef runs correctly! |
Closing this one out. The change required in the |
@rowanmiller Thanks for the details. Here's a nuance: I'm having the same issue but my project is Asp.net Core on .Net Framework 4.6.1, and it seems EF.Tools.DotNet:1.1.0* is not available for net461. What dependencies and tools should I specify to be able to run ef commands? |
@bricelam could you help out with the above question? |
For now, you need to add it manually to the csproj (NuGet will enable installing from the UI later). <ItemGroup>
<DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="1.0.0-msbuild3-final" />
</ItemGroup> |
Following this guide but changing version on package Microsoft.EntityFrameworkCore.Tools to the preview3 when executes "dotnet ef" after "dotnet restore" fires up this error: No executable found matching command "dotnet-ef". And when I rollback to the preview2 but along with the package Microsoft.EntityFrameworkCore.Design on version 1.1.0-preview1-final gave another error dotnet quit unexpectedly (on window alert) and message error on terminal says: Unhandled Exception: System.MissingMethodException: Entry point not found in assembly 'Microsoft.EntityFrameworkCore.Design, Version=1.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
this occurs on "dotnet ef" after "dotnet restore"...
All this with Visual Studio Code on macOS Sierra
BTW this is my project.json that works well on dotnet ef execution and this is for a web api project
The text was updated successfully, but these errors were encountered: