Problem with dotnet cli ef tools after upgrading to vs 2017 15.4.4 and november .net core rollup

[spnm]

Not sure if its an EFCore issue or cli

Steps to reproduce

Using Visual Studio Enterprise 2017 (v 15.4.4)

Add migration

dotnet ef migrations add [MigrationName]

Expected behavior

Migration created

Actual behavior

Error message :
The specified framework version '2.0' could not be parsed
The specified framework 'Microsoft.NETCore.App', version '2.0' was not found.
Check application dependencies and target a framework version installed at:
\
Alternatively, install the framework version '2.0'.

My project is a console library and the content of .csproj file is below:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>
  
  <ItemGroup>
    <PackageReference Include="System.Reflection.Metadata" Version="1.5.0" />
    <PackageReference Include="Microsoft.Extensions.Configuration" Version="2.0.0" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="2.0.1" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="2.0.1" PrivateAssets="All" />
  </ItemGroup>
  
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.1" />
  </ItemGroup>
</Project>

So i tried to use global.json in the root of my project :

{
  "sdk": {
    "version": "2.0.3"
  }
}

and the error was the same.
But when I changed global.json content to this :

{
  "sdk": {
    "version": "2.0.2"
  }
}

It worked.

[zd-dalibor]

I have the same problem.

[marcwmiller]

I have same issue.

[lccarvalho]

Scaffold-DbContext fails silently after that same upgrade to VS 15.4.4

[Wind010]

I have the same predicament.

Error is occurring when running:
dotnet ef migrations remove

I was able to work around this by adding this to the EF project:

<PropertyGroup>
   <TargetFramework>netcoreapp2.0</TargetFramework>
   <RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion>
</PropertyGroup>

[alexzaytsev-newsroomly]

Can confirm that 2.0.2 workaround works. Not really clear why.

[jorgeyanesdiez]

I am pretty sure this is a CLI (dotnet tools) problem, not an EF problem, since I get the same error with dotnet xunit in powershell.

I have cleaned up my system, and only have the 2.0.3 SDK, runtime (x64 and x86) and windows server hosting packs, therefore, @spnm 's solution doesn't work, but @Wind010 's does.

[jorgeyanesdiez]

This is probably a dupe of https://github.com/dotnet/cli/issues/7901

[ajcvickers]

@Eilon @natemcmaster @livarcocc Any ideas on this?

[livarcocc]

I have been trying to repro this for a while now without much success, but this does seem like a CLI problem.

[livarcocc]

This is a CLI/SDK bug that we now understand. I am duping this one to the one in the CLI: https://github.com/dotnet/cli/issues/7901

We will explain it there why this happens and a workaround and we are figuring out the vehicle to carry a fix for this.

@ajcvickers can you close this bug?

[ajcvickers]

Thanks @livarcocc. Closing.

[bricelam]

Re-opening since it looks like there's work to do on our side.