*Going forward, you should only be using project.json with. After March 7 release, this will just be “1.0.0”.
If you are using project.json*, make sure that you have the Tools.DotNet package in the Tools section, not the dependencies section. This is explained in the course demos, but still a step you may overlook in your excitement! Make sure that you are running the command from the folder that contains the project where the Tools package is referenced. NET framework, then you’ll need to use the PowerShell commands e.g. If you’re following my course, that’s explained. is for the CLI (dotnet commands)īe sure you’ve referenced the Tools.DotNet version of the package so that you have access to the CLI commands. The current stable tooling for EF Core migrations is split into two packages. There are a few key things to watch out for. While some of these notes are specific to the project.json use in the course, I’ve also added tips for using dotnet ef with the newer csproj/msbuild support. Problems You May Encounter with ‘dotnet ef’ I worked through these with them but wanted to write down the suggestions I’d made and have a single blog post I could point to. Of the nearly 2000 who have already watched the course since it’s release less than 2 weeks ago, a few people ran into some confusion with the versioning and getting the “no executable found” message. The course’s focus is on EF Core, so as long as I could hand-hold users through the project.json setup stuff without the need to make them expert at that, it was the right way to go. But Pluralsight and I both agreed that it made sense not to ALSO force users to the bleeding edge, not even released VS2017 for the demos. So in the course means that we’re stuck with project.json support and tooling that’s not quite aligned. VS2015 only supports project.json and the project templates set you up for. 
While I did recreate the VS2017 demos in RC3 right before we published the course, we chose to leave the rest of the. I recorded my Entity Framework Core: Getting Started course on Pluralsight while VS2017 was still in beta. The tooling for VS2015 is outdated and there are no plans to bring them up-to-date for the new csproj support. The most common one is No executable found matching command "dotnet-ef" A Note If Your Coming from My Pluralsight EF Core Course
NET core), it’s easy to run into a problem when attempting to use EF Core migrations at the command line. NET Core app (ASP.NET Core or other app sitting on. Updated Maafter Visual Studio 2017 was released.Īlso, keep in mind that I have been updating this post (and will continue to do so) as I discover new ways people are hitting problems with dotnet ef.
0 kommentar(er)
