Is this a new bug?
Current Behavior
If your package with this dependency is included into an ASP.NET Core 2.1 (.NET Framework) ecosystem and I try to fix downgrade error forcing My dependency with same Logging 8.0.1 version then ASP.NET Core 2.1 will be broken because backward compatibility is not available to Logging 2.1.1 version.
I suggest to reference Microsoft.Extensions.Logging.Abstractions 2.1.1 instead of 8.0.1, forward compatibility is available and ASP.NET Core 2.1 on .NET Framweork App will result compatibile too.
If you want I can propose these changes in a PR.
Expected Behavior
I'm expecting to to add your package in a .NET Framework app with ASP.NET Core 2.1 with no downgrade package errors.
Steps To Reproduce
- Create a .NET FRamework App with ASP.NET Core 2.1 (supported yet)
- Add reference to package APIMatic.Core 40.0
- Try to fix downgrade error adding ref to package Microsoft.Extensions.Logging.Abstractions 8.0.1
- APIs throw exception: "Could not load type 'Microsoft.Extensions.Logging.Abstractions.Internal.NullScope' from assembly 'Microsoft.Extensions.Logging.Abstractions, Version=8.0.0.1, Culture=neutral, PublicKeyToken=adb9793829ddae60'"
Environment
- **OS**: Windows 11
- **.NET Version**: 4.7.2
- **SDK Name**: 9.0.103
Relevant log output
Additional Context
No response