NLog.Extensions.Logging | NLog as Logging Provider for Microsoft Extension Logging

You can try to disable the filter-logic in Microsoft LoggerFactory by changing from:

Deleting and re-installing all of the packages just solved my problem.

Use Pomelo for MySQL 6.0.0 instead just worked.

Yes there was some discussion about whether XML-config and JSON-config should be completely 1-to-1. See also: https://github.com/NLog/NLog.Extensions.Logging/pull/283

Because JSON-config represented targets-section as a dictionary of known target-names, then it didn't feel natural to have default-wrapper and default-target-parameters as reserved magic-strings.

1. Instead they were moved out of targets-section, as you have discovered from the documentation.
2. Yes all items in the targets-section will be wrapped, when using default-wrapper.
3. Have not tested what happens if placing default-wrapper and default-target-parameters inside the targets-section-dictionary. Maybe check the NLog InternalLogger whether it complains about unknown configuration-items.

Notice more work is being done to give default-wrapper and default-target-parameters a better name, since it might not be easy to guess that they both apply to the targets-section. See also: https://github.com/NLog/NLog.Extensions.Logging/pull/500

For ${configsetting} you need at least the package NLog.Extensions.Logging or one of the dependent packages like NLog.Web.AspNetCore or NLog.Extensions.Hosting.

Normally you would use .UseNLog() on IHostBuilder, see NLog - Getting started with ASP.NET Core 3

To manual register the Microsoft Extension IConfiguration with ${configsetting}:

In this case, the logging is not an "external tool", it is a part of the application. That's why you can't implement a "generic" logging, you have to have it compiled into your app. But you are not limited to only one. You could compile in all three of them, and during the startup initialize the one you need based on the configuration

For the plain file log, there are no types, so My custom string and 42 will be printed as just those values: My custom string and 42 (don't get confused by the quotes in the documentation)

Some layouts support types, like the JSON layout.

For example:

The easy way, but will have a performance hit (Notice ${mdlc:item=module} is case-sensitive)

Make sure to use Unix-path, so stop using backslash \

Ex. instead of ${logDir}\log-${shortdate}.log then it should be ${logDir}/log-${shortdate}.log.

If still having issues then try to activate the NLog InternalLogger and check the output https://github.com/NLog/NLog/wiki/Internal-Logging