Closed robotgryphon closed 6 months ago
Sadly enough then .NET Framework have become the friend, that no one wants to hang out with. Microsoft have decided that .NET 4.6.1 (and newer) can be used to create ASP.NET Core2.1 Applications.
One solution is to explicit include "Microsoft Extensions Logging"-nuget-package (ver. 8.0) to the "Project" together with "Nlog.Extensions.Logging" (ver. 5.3.8).
Another solution is updating "Project" from .NET Framework to .NET8.
Closing issue due to inactivity.
Type (choose one):
NLog version: 5.2.8 NLog.Extensions.Logging version: 5.x.x NLog.Web.AspNetCore version: not used Platform: .NET Framework 4.8
As the title states, right now if you use NLog.Extensions.Logging in a .NET 4.8 project along with anything else that targets the Microsoft dependency injection libraries, you end up with a nasty runtime DLL conflict due to this library's old usage of
Microsoft.Extensions.Logging 2.1.x
. See below: