[master] Update dependencies from aspnet/EntityFrameworkCore

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/aspnet/EntityFrameworkCore

• Build: 20200106.1
• Date Produced: 1/6/2020 2:13 PM
• Commit: c2406e783e3764e0435980a2a695a12286838b27
• Branch: refs/heads/master
• Updates:
  • Microsoft.EntityFrameworkCore.Tools -> 5.0.0-alpha.1.20056.1
  • Microsoft.EntityFrameworkCore.SqlServer -> 5.0.0-alpha.1.20056.1
  • dotnet-ef -> 5.0.0-alpha.1.20056.1
  • Microsoft.EntityFrameworkCore -> 5.0.0-alpha.1.20056.1
  • Microsoft.EntityFrameworkCore.InMemory -> 5.0.0-alpha.1.20056.1
  • Microsoft.EntityFrameworkCore.Relational -> 5.0.0-alpha.1.20056.1
  • Microsoft.EntityFrameworkCore.Sqlite -> 5.0.0-alpha.1.20056.1

Coherency Updates

The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format

• Microsoft.NETCore.App.Internal -> 5.0.0-alpha.1.19562.8 (parent: Microsoft.Extensions.Logging)

[rynowak]

@aspnet/build - should this be closed? Seems redundant with #17641

[Tratcher]

Blocked due to 3.1 dependency issues in EF. We need to wait for runtime dependencies to start flowing again.

[wtgodbe]

Updated to include workarounds from #17641

[BrennanConroy]

Blocked on dotnet/runtime#1129 flowing to EF and then EF updates coming to this PR.

[ryanbrandenburg]

In addition to dotnet/runtime#1129, this is seemingly blocked by a failure within the EF migration tool:

Project new razor --auth Individual failed to run EF migrations.
Process exited with code -2147450730
StdErr: It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '3.1.0' was not found.
 - The following frameworks were found:
 5.0.0-alpha.1.19562.8 at [F:\workspace\_work\1\s\.dotnet\shared\Microsoft.NETCore.App]
 5.0.0-alpha.1.19564.1 at [F:\workspace\_work\1\s\.dotnet\shared\Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The specified framework can be found at:
 - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=3.1.0&arch=x64&rid=win10-x64\

StdOut: 
Expected: True
Actual: False

@ajcvickers was a new dependency on 3.1 added to the migrations tool?

[ajcvickers]

@ryanbrandenburg Not that I am aware of. @bricelam Any ideas?

[ajcvickers]

Looking at this some more, why are EF dependencies being upped to 5.0? EF Core for the time being is a set of .NET Standard 2.1 libraries together with tooling built against .NET Core 3.1. We want to keep it this way, at least until closer to the 5.0 release when we will revisit what we target.

[ajcvickers]

Looks like this is reverting some of the changes we made to pin 3.1.

Sorry, got confused. :-) However, EF Core 5.0 for now should continue to depend on .NET Standard 2.1, released 3.1 packages, and tooling that needs .NET Core 3.1. Nothing should require 5.0.

[dougbu]

this is seemingly blocked by a failure within the EF migration tool

@ryanbrandenburg that's the known issue which @Tratcher commented on in #17947 (comment) Basically the dotnet ef tool doesn't build with a runtimeconfig.template.json file, giving it the default roll-forward behaviour: It'll only roll forward to the next minor release. Since it's built to target netcoreapp3.1 (see https://github.com/aspnet/EntityFrameworkCore/blob/master/Directory.Build.props#L16), that means it can't currently run against netcoreapp5.0 runtime.

@ajcvickers

Looking at this some more, why are EF dependencies being upped to 5.0?

Dependencies from EF aren't being changed here. However those from Extensions must align with the rest of AspNetCore i.e. target netcoreapp5.0. Oddities creep in because the EF tooling is incompatible w/ netcoreapp5.0.

---

@ajcvickers @bricelam my preference here would be a near-term fix in EF Core allowing the tools to roll forward on major version i.e. from 3.1 to 5.0. If that happened, this repo and any customers targeting netcoreapp5.0 wouldn't need tooling workarounds.

[dougbu]

Another option might be to change https://github.com/aspnet/EntityFrameworkCore/blob/master/src/dotnet-ef/dotnet-ef.csproj#L15 to use netstandard2.1 instead of $(DefaultNetCoreTargetFramework).

[ajcvickers]

@bricelam

my preference here would be a near-term fix in EF Core allowing the tools to roll forward on major version i.e. from 3.1 to 5.0.

Any reason we don't want the tool to roll forward anyway, long term?

[JunTaoLuo]

cc @halter73

[jkotalik]

I just started my buildops rotation. Is this still blocked?

[dougbu]

Is this still blocked?

Yes. Need the dotnet/runtime changes to flow into this repo before this PR is likely to build correctly. @wtgodbe please correct me if I'm wrong.

[wtgodbe]

I think we can close this one in favor of #18247

[dougbu]

Agreed @wtgodbe. Though I had both issues open, I forgot we had a newer PR to watch.

@jkotalik my comment applies to #18247 as well.