UseNLog() in 4.5.0-beta01 removes ConsoleLogger from .Net Core

[agentschmitt]

After updating from NLog.Web.AspNetCore 4.3.1 to 4.5.0-beta01, the ConsoleLogger from .NET does no longer work.
"CreateDefaultBuilder" adds the ConsoleLogger by default, but after i am adding "UseNlog" no messages are logged to console any more.
Does Nlog Registration remove the Loggers already registered?
Maybe this issue is related? "Add option to remove other loggers #192"

This is my Nlog Setup, created as descriped in https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-2

            var logger = NLogBuilder.ConfigureNLog("NLog.config").GetCurrentClassLogger();

            var hostBuilder = WebHost.CreateDefaultBuilder(args)
                .UseStartup<Startup>()
                .UseNLog();

[304NotModified]

Have you check this. We don't remove any logger. Probably the issue is the custom log factory

[304NotModified]

Thanks again for reporting!

[snakefoot]

When using GetCurrentClassLogger() then one is no longer using Microsoft Extension Logging, but writing directly to the NLog-engine, maybe this is the confusing part?

[304NotModified]

I found the issue (but not yet how to solve)

in asp.net 2 we register NLogLoggerFactory, instead of NLogLoggerProvider. - this will replaces Microsoft's loggerFactory.

This is a more clean way, but the side-effect is that addConsole is not working and that loggers that were register on (Microsoft's) loggerFactory are gone.

[304NotModified]

fixed in beta 2