NLog.Extensions.Logging
NLog.Extensions.Logging copied to clipboard
NLog
NLog as Logging Provider for Microsoft Extension Logging
Where NetStandard2.1 uses NetCore3.1 dependencies.
When receiving LogEvent that both contains message-template-parameters and EventId, then NLog will allocate both a message-template-parameter-array and also message-properties-dictionary (for eventid). Maybe consider injecting EventId into the list of message-template-parameter,...
Has been introduced with NET6, but it should be "easy" to implement equal solution in NLog.Internal: From: ```c# if (factory is null) { throw new ArgumentNullException(nameof(factory)); } ``` To ```c#...
This fixes https://github.com/NLog/NLog/issues/5469 When config file has empty sections like this ``` { "NLog": { "throwConfigExceptions": true, "variables": {}, "extensions": [], "targets": {}, "rules": [] } } ``` Those sections...
Could be nice if one could do this: ```json { "NLog": { "throwConfigExceptions": true, "targets": { "logconsole": { "type": "Console" }, "email": { "type": "mail" }, "bothTargets": { "type": "SplitGroup",...
**Type** (choose one): - Feature request **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...
Just like `${level}` but mapping to to Microsoft LogLevel-string-values: - **Critical** - **Debug** - **Error** - **Information** - **None** - **Trace** - **Warning** Maybe consider introducing a short enum-version (Matches...
Trying to resolve #759 by avoiding double-registration on the config-changed-event.
**Type**: Bug **NLog version**: 5.3.3 **NLog.Extensions.Logging version**: 5.3.12 **Platform**: .NET 6.0 **To reproduce**: *csproj* ```xml Exe net6.0 enable enable Always ``` *main.cs* ```c# using Microsoft.Extensions.Configuration; using NLog.Extensions.Logging; var config =...
