-
|
Here's how I reference Microsoft.EntityFrameworkCore: While the latest version is Here's the output of Should not the direct dependency on |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
It looks like you're using Central Package Management (CPM) which does not set the versions for transitive package references by default. NuGet reads the <PackageReference Include="Microsoft.EntityFrameworkCore" />The corresponding If you do not want to have to specify an explicit Another note is that floating versions are not allowed in CPM by default either, but can be enabled if needed. https://learn.microsoft.com/nuget/reference/errors-and-warnings/nu1011 |
Beta Was this translation helpful? Give feedback.
-
|
But that's what I am saying, I already have direct package reference in my project.
From |
Beta Was this translation helpful? Give feedback.
-
|
I'm not able to reproduce that problem. I have this project: <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<RestorePackagesWithLockFile>true</RestorePackagesWithLockFile>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="EFCore.NamingConventions" Version="8.0.3" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Relational" Version="8.0.13" />
<PackageReference Include="Npgsql.EntityFrameworkCore.PostgreSQL" Version="8.0.11" />
</ItemGroup>
</Project>Transitively, those packages reference <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<RestorePackagesWithLockFile>true</RestorePackagesWithLockFile>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="EFCore.NamingConventions" Version="8.0.3" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Relational" Version="8.0.13" />
<PackageReference Include="Npgsql.EntityFrameworkCore.PostgreSQL" Version="8.0.11" />
<PackageReference Include="Microsoft.EntityFrameworkCore" Version="8.*" />
</ItemGroup>
</Project>packages.lock.json "Microsoft.EntityFrameworkCore": {
"type": "Direct",
"requested": "[8.*, )",
"resolved": "8.0.14",
"contentHash": "HNn+NPKCm7rR7ij7IRCCbuImaMulFJGloyIbMwi3Ews77RsthM8gxpTZciFLgRYPsBtszKpdIClEwnWmP0vjUg==",
"dependencies": {
"Microsoft.EntityFrameworkCore.Abstractions": "8.0.14",
"Microsoft.EntityFrameworkCore.Analyzers": "8.0.14",
"Microsoft.Extensions.Caching.Memory": "8.0.1",
"Microsoft.Extensions.Logging": "8.0.1"
}
}, |
Beta Was this translation helpful? Give feedback.
-
|
But in combination with CPM? Project: |
Beta Was this translation helpful? Give feedback.
-
|
Hm... after switching to floating minor version for Npgsql it resolves to 8.0.14 ... But Npgsql does not even have EF core as dependency. I am perplexed. Here's another example: Project file In And the most confusing is the combination of this: and this In resolves either to 7.3.1 or to 7.3.2 for direct dependency. And pay attention to the part: It says that |
Beta Was this translation helpful? Give feedback.
It looks like you're using Central Package Management (CPM) which does not set the versions for transitive package references by default.
NuGet reads the
<PackageReference />items as direct dependencies and selects the versions that you specify. For each child dependency, it reads that package to get the list of its dependencies. To override the package version of a transitive package reference, you must specify an explicit package reference to it. In this case, adding this to the project should work:The corresponding
<PackageVersion />item would then specify the version.If you do not want to have to specify an explicit
Pack…