Closed N-Olbert closed 2 years ago
@N-Olbert Thank you for raising the issue. We will address as part of the .NET 6 upgrade in #45.
@N-Olbert @tonysneed According to this document, .NET 6 supports .NET Standard 2.1 : https://dotnet.microsoft.com/platform/dotnet-standard. The current version used .NET Standard 2.0.
Also, it's kind of confusing because I read that there is no version of .NET Standard that is compatible with .NET 6.0. Nevertheless, for urgent needs you can use this forked package compiled for .NET 6 : https://www.nuget.org/packages/TrackableEntities.EF.NET6/
Tony would you made an update to this repository ?
Good idea! Let me try …
@samantha-letourneau @tonysneed Just for reference: .NET 6 supports .NET Standard 2.1, but EF Core 6 does not:
EF Core 6.0 requires .NET 6. EF Core 6.0 does not target any .NET Standard version; for more information see the future of .NET Standard. Link
This is also different to EF Core 5, which supported .NET Standard 2.1, as the following table indicates
EF Core | 3.1 | 5.0 | 6.0 |
---|---|---|---|
.NET & .NET Core | 3.1 | 5.0 | 6.0 |
.NET Standard | 2.0 | 2.1 |
TLDR: I'm not sure if moving to .NET Standard 2.1 is enough, maybe it is required target .NET 6 directly
@N-Olbert You're right ... we'll need to port to .NET 6 for EF Core 6 compatibility. I'll get to work finalizing #45.
@N-Olbert I checked and IsUnique
property still exists on IReadOnlyForeignKey
interface.
Hello,
are there any plans to support EF Core 6?
Currently it seems that only EF Core 5 is fully supported, f. e. on EF Core 6 we get the following error message:
For this concrete problem the reason is the following method: https://github.com/TrackableEntities/TrackableEntities.Core/blob/2d8ae52eb6c1b4662bc7390405a6e2e1dfaf0114/TrackableEntities.EF.Core/NavigationExtensions.cs#L16-L23
While the ForeignKey-property still exists within the INavigation-Interface, the IsUnique-Property does not! Looking at the IForeigenKey-Interface documentation reveals that the IsUnique-property was present in EF Core 5, but does no longer exist in EF Core 6.