Closed TanvirArjel closed 3 years ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
more context: here is the repo https://github.com/TanvirArjel/EFCore.GenericRepository and here is the commit that should fail https://github.com/TanvirArjel/EFCore.GenericRepository/commit/0323871b35e5a49c197a83e1869ccf74c7a7a110
as for the bug, it is weird. so only v6 of microsoft.extensions.logging
has analyzers. ie earlier versions do not. so it seems to be conflating "v6 has analyzers" with "the microsoft.extensions.logging nuget has analyzers"
@TanvirArjel as for a solution for you.... the current assumption of TanvirArjel.EFCore.GenericRepository
is that: wanting to consume a certain version of the runtime implies someone wants to ref a corresponding version of ef. this is not correct. eg i might want to use ef 3 on net 6. So i recommend either only supporting one version of ef, or (if u want to keep supporting many) release named nugets that correspond to the ef version eg TanvirArjel.EFCore6.GenericRepository
and TanvirArjel.EFCore5.GenericRepository
etc
i think this is a duplicate of https://github.com/dotnet/runtime/issues/53297
@SimonCropp The solution you have provided is not realistic anyway.
Is this a dup of https://github.com/dotnet/sdk/issues/18148 ?
@krwq Why it is in Milestone 7.0.0
? Then how shall we update our packages to support v6.0.0
. Currently, adding support for the .NET 6.0 in our NuGet packages does not work due to this blocking issue.
@krwq This is a blocking issue. Download this this repository and enable .NET 6.0 support and build. You will see the build failed.
@krwq
Is this a dup of dotnet/sdk#18148
Yes! Seems so.
Closing this issue as a dup of: https://github.com/dotnet/sdk/issues/18148 which was fixed and the fix should be available on the Preview7 SDK.
Suddenly I am receiving the following warning and error:
Warning:
Error:
Project files is:
If I remove
.NET 6.0
from TargetFrameworks then both warning and error go away.However, How can I fix the issue right now without removing .NET 6.0 support?