NET Core 1.1 installed: The specified framework '', version '1.1.0' was not found. Here’s an example of what the dotnet ef command will tell you if you don’t have. NET Core SDK tools will also be released so the versions will just be normal numbers like 1.0.0. Note that on March 7 when VS2017 has its official release, the. NET Core SDK tools are still in preview so the version number of the current “stable” build that goes with. NET Core 1.1 installed and the related dotnet SDK – which is not numbered as simply. (I’m in the process of updating the course to use the new 1.0.0 package) In my EF Core course, I’m using EF Core 1.1 and for EF tools and in all but the last module, I’m using 1.0.0-preview4. Make sure that the version of the EF Core tools you are using aligns with the version of.A twitter friend accidentally ran into this problem and was getting the “no executable found” error message. Migrations only work with those and not, for example, InMemory. Be sure you’re targeting a relational database.After March 7 release, this will just be “1.0.0”. Īs of VS2017 RC3 (which is what I show in the last module of the course) it was possible to use msbuild3 as shown in point #4 above and the CLI commands. Therefore you have to use the Tools package and work in the package manager console, not the command line. If you are using an older Release Candidate of Visual Studio 2017 (before RC3), the CLI tooling was not yet aligned with the msbuild support so with that version, you have to use the PowerShell commands to do migrations. You shouldn’t be using an RC of VS2017 at this point but I’m leaving this one here.Here’s an example where that bit someone. It’s possible that you have to Tools correctly placed but your IDE did not trigger a dotnet restore.If you’re using csproj/msbuild, make sure the casing is correct if you’re manually adding that package in csproj! I’ve seen people get tripped up by typing Dotnet rather than DotNet.After March 7 release, this will just be version “1.0.0”. If you’re using csproj/msbuild, make sure the tools package is listed in the DotNetCliToolsReference tag.
NET Core (1.1+) you should be using csproj/msbuild. *Going forward, you should only be using project.json with.
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)
