Rolf Kristensen
Rolf Kristensen
The NLog ILogger-interface is crazy huge. Lets slim it down by just providing generic Log-methods.
If wanting to refresh the cached-value every 1 minutes. Then one can do this: `${local-ip:cachedSeconds=60}` But if wanting to refresh the cached-value every day (or every hour), then things get...
NLog 5.0 allows one to resolve an instance of the `IJsonConverter`-interface. This is great, and is a first step towards making `DefaultJsonSerializer` an internal class. This means a custom Layout...
Remove the following dependencies from NLog-core: `` See also #2729, #2296 and #1314 For NLog 6.0
**Current NLog config** (xml or C#, if relevant) ```xml ``` - What is the current result? `Required parameter "WrappedTarget" was not specified` - What is the expected result? `Should say...
This makes it impossible to complete `LogManager.Shutdown()` It will correctly complain with timeout error on Flush using threadpool-threads. But afterwards when closing all targets then it will get stuck in...
Have an application that writes several GByte data using NLog as part of startup-rutine. After startup-rutine has completed, and just about to go online, then it performs a blocking garbage...
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,...
https://github.com/MindscapeHQ/raygun4net/blob/0f232cd9829bcda2d769ae7a26249a149a041d12/Mindscape.Raygun4Net4/RaygunClient.cs#L335 Should avoid populating ThreadStatic variables for ThreadPool-Threads. Passing parameters using global variables is generally a bad idea.