v16.3.2 can be incompatible with EF Core 3.1 projects
See original GitHub issueDescribe the bug We upgraded Audit.EntityFramework.Core from v16.2.1 to v16.3.2 and it seems to be incompatible with our build because we’re not using EF 5.
error NU1605: Detected package downgrade: Microsoft.EntityFrameworkCore.Abstractions from 5.0.1 to 3.1.10. Reference the package directly from the project to select a different version.
error NU1605: Audit.NET.16.3.2.BugReport -> Audit.EntityFramework.Core 16.3.2 -> Microsoft.EntityFrameworkCore 5.0.1 -> Microsoft.EntityFrameworkCore.Abstractions (>= 5.0.1)
error NU1605: Audit.NET.16.3.2.BugReport -> Microsoft.EntityFrameworkCore.Abstractions (>= 3.1.10)
To Reproduce https://github.com/bhanson-techempower/Audit.NET.16.3.2.BugReport
Expected behavior ASP.NET/EF Core 3.1 is the latest LTS build. I would expect a major version bump from Audit.NET for the underlying bump to .NET 5.
Libraries (specify the Audit.NET extensions being used including version):
- Audit.EntityFramework.Core: 16.2.1 or 16.3.2
- Microsoft.EntityFrameworkCore.Abstractions: 3.1.10
Target .NET framework:
- .NET Core 3.1
Additional context For now, we’ll stay on v16.2.1.
Thank you!
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Package Microsoft.EntityFramework.Core 6.0.0 is not ...
Open your project in Visual studio and then go to Tools->Nuget Package ... 5.0 or below is not supported by or compatible with...
Read more >Supported .NET implementations - EF Core
Information on supported platforms across Entity Framework Core versions. ... NET Upgrade Assistant can help you with the migration process.
Read more >MSB3277: Found conflicts between different versions of ' ...
This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the...
Read more >Microsoft to End Support for .NET Core 3.1 in December 2022
The long-term-support (LTS) version 3.1 of Microsoft .NET Core Framework is slated to go out of support on December 13th, 2022.
Read more >Upgrading from ASP.NET Core 3.1 to 5.0 (Preview 1)
In this post, I cover the steps required to upgrade some projects from the ASP.NET Core 3.1 to the first preview of .NET...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
oh you’re right, I’ve fixed that on version 16.4.3, please upgrade your references and re-test
I’ve created two new packages for this purpose; when you need to use version 3 of Entity Framework Core, but are targeting .NET Standard >= 2.0.
In that case you must reference the packages ending with
.v3
Audit.EntityFramework.Core.v3
orAudit.EntityFramework.Identity.Core.v3
Please update your references to use this new package (starting on version 16.4.0) and re-test