Aspnetcore: Dependencies impossible to satisfy for Microsoft.AspNetCore.Identity.EntityFrameworkCore, Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore in connection with Microsoft.EntityFrameworkCore.Relational

Created on 19 Feb 2020  ·  10Comments  ·  Source: dotnet/aspnetcore

Describe the bug

Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore and Microsoft.AspNetCore.Identity.EntityFrameworkCore both have requirement of:
Microsoft.EntityFrameworkCore.Relational (>= 3.1.2)
which is not yet release and because of that dotnet restore phas fails

To Reproduce


In *.csproj Try to reference
<PackageReference Include="Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore" Version="3.1.2" />
and/or
<PackageReference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="3.1.2" />
which are relased and observe that tahy can not load
<PackageReference Include="Microsoft.EntityFrameworkCore.Relational" Version="3.1.2" />

Further technical details

  • ASP.NET Core version : 3.1.101
  • Include the output of dotnet --info

dotnet --info
Zestaw .NET Core SDK (odzwierciedlenie dowolnego pliku global.json):
Version: 3.1.101
Commit: b377529961

▒rodowisko uruchomieniowe:
OS Name: Windows
OS Version: 10.0.17763
OS Platform: Windows
RID: win10-x64
Base Path: C:Program Filesdotnetsdk3.1.101

Host (useful for support):
Version: 3.1.1
Commit: a1388f194c

.NET Core SDKs installed:
2.2.207 [C:Program Filesdotnetsdk]
3.1.101 [C:Program Filesdotnetsdk]

.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.15 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.15 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.1 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.15 [C:Program FilesdotnetsharedMicrosoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:Program FilesdotnetsharedMicrosoft.NETCore.App]
Microsoft.NETCore.App 3.1.1 [C:Program FilesdotnetsharedMicrosoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.1 [C:Program FilesdotnetsharedMicrosoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

  • The IDE (VS / VS Code/ VS4Mac) you're running on, and it's version
    VS 2019 -version 16.4.5
area-infrastructure area-platform

Most helpful comment

Same for the package Microsoft.AspNetCore.DataProtection.EntityFrameworkCore.
It has a dependency to Microsoft.EntityFrameworkCore with version >= 3.1.2 which cannot be resolved.

All 10 comments

image

Same for the package Microsoft.AspNetCore.DataProtection.EntityFrameworkCore.
It has a dependency to Microsoft.EntityFrameworkCore with version >= 3.1.2 which cannot be resolved.

Same for Microsoft.EntityFrameworkCore.Sqlite:

image

Maybe issue should be filed in EntityFrameworkCore repo?

Same for Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore

"someone" forgot to do new package for https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Relational/

@ChaosEngine thanks for contacting us.

@dotnet/aspnet-build We do have an issue related to this, don't we?

@anurse is this the same issue as the sql cache global tool issue?

@anurse @ajcvickers were EF packages released yesterday? This looks very much like a gap in the release.

@javiercn this is unrelated to the global tool issue. That was about dependencies on the latest shared framework while this is about missing packages on NuGet.

@dougbu No EF packages were released. There weren't any EF fixes, and my last understanding from talking to @Pilchie was that other packages were supposed to reference 3.1.0 rather than 3.1.x, so I assumed it was by design that we didn't push new packages. We probably just need to push the EF packages.

FYI that @anurse got these published this morning, so as NuGet.org ingests them, this issue should be mitigated.

@ajcvickers Other packages are supposed to reference 3.1.0, but we haven't made that switch yet.

done 31 minutes ago

Was this page helpful?
0 / 5 - 0 ratings