Introduced AddNLogWeb to avoid conflict with AddNLog from NLog.Extension.Logging

[snakefoot]

Reduce the level of confusion when used within services.AddLogging()-method. See also NLog/NLog#4090

Like this:

            services.AddLogging(loggingBuilder =>
            {
                loggingBuilder.ClearProviders();
                loggingBuilder.AddNLogWeb(); // fix Missing serviceProvider, so no HttpContext
            });

Instead of this:

            services.AddLogging(loggingBuilder =>
            {
                loggingBuilder.ClearProviders();
                loggingBuilder.AddNLog(provider => null);  // fix Missing serviceProvider, so no HttpContext
            });

Guess when NLog.Extension.Logging ver. 2 with released with NLog ver. 5.0, then AddNLog can be marked as obsolete (Redirect to AddNLogWeb)

[sonarqubecloud]

SonarCloud Quality Gate failed.

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

0.0% Coverage
0.0% Duplication

[snakefoot]

An alternative could be to also have LoadConfigurationFromSection in NLog.Web-namespace. Thus avoiding the need to have both using NLog.Web and using NLog.Logging.Extensions (Continue to have methods with name-conflicts, but making it obvious that they have different features)

[304NotModified]

An alternative could be to also have LoadConfigurationFromSection in NLog.Web-namespace. Thus avoiding the need to have both using NLog.Web and using NLog.Logging.Extensions

Related: NLog/NLog.Extensions.Logging#421

[304NotModified]

An alternative could be to also have LoadConfigurationFromSection in NLog.Web-namespace. Thus avoiding the need to have both using NLog.Web and using NLog.Logging.Extensions (Continue to have methods with name-conflicts, but making it obvious that they have different features)

That's fine, in the end we will move everything to Microsoft.Extensions.DependencyInjection namespace, see NLog/NLog.Extensions.Logging#421. But that will be the next major version I guess