Apache log4net 2.0.17 addresses reported issues:

Bug fixes

• NullRefException from shutdown in 2.0.16 fixed in Fast fix for NullRefException from FileAppender" (by @erikmav )"

Complete diff

A big thanks to @FreeAndNil for doing all the hard work of collating changes.

Bug fixes

• Support converting '.NET TP Worker' to the numeric thread ID on .NET 8+ (by @erikmav )
• Fix typo in RemotingServer App.Config (by @craigdfrench )
• Fix CodeQL Password in configuration file Rule False Positives (by @justinmichaels )

Enhancements

• adding extension points for revising logged content (by @FreeAndNil )
• SystemInfo.EntryAssemblyLocation writable to adjust location for config-files in unit test projects (by @FreeAndNil )
• New locking model for single log file in native applications with managed parts (by @FreeAndNil )
• Extension point for handling new lines in RemoteSysLogAppender added (by @FreeAndNil )
• Defer creation of locking model to ActivateOptions() (by @FreeAndNil )
• Add Peek() method to ThreadContextStack and LogicalThreadContextStack (by @andreycha )

Attention : .NET 3.5 Client Profile is no longer supported . I'm really sorry, I've tried to keep as many of the legacy targets available as possible, but after spending another 4 or so hours trying to get net35-client to build on any machine, I've given up - as far as I'm aware, this should only affect Windows XP clients. I'm afraid 2.0.14 was the end of the road for you. Apache log4net 2.0.15 addresses reported issues:

Bug fixes

• Improper usage of xml namespacing for netfx targets after a netstandard update ( LOG4NET-685 , related LOG4NET-683 )
• Locking hashtables during write in RenderMap calls to make them thread-safe ( LOG4NET-646 )
• An issue where RollingFilAppender would sometimes overwrite files instead of rolling them ( LOG4NET-672 )

Enhancements

• Enforce TLS1.2 in the ps1 scripts provided for dev use
• Corrected links in README
• Open up the internals of LogEvent a bit for extension purposes
• Add information about FixFlags and performance to the BufferingAppender (and derivative) documentation

• Pull request by @NicholasNoise to address issues with logging via ado appender to PostgreSQL
• Community request to correctly handle null data in ReadOnlyPropertiesDictionary
• Pull request by @erikmav to use the numeric thread id for .net worker pool threads ( LOG4NET-680 )
• Pull request by @erikmav to dispose of WindowsIdentity retrieved in TryGetCurrentUserName() ( LOG4NET-671 )

Some minor updates:

• address deadlock with rolling file appender ( https://issues.apache.org/jira/browse/LOG4NET-583 )
• performance improvement for platforms not supporting WindowsIdentity ( https://issues.apache.org/jira/browse/LOG4NET-652 )
• allow using the netstandard2.0 libraries from within asp.net on net472 ( #76 )
• update to the log4j-alike output ( #18 )

This is essentially the same release as rc-1, with the artifacts updated so that unzipping them won't scatter files in the target.

Some minor updates:

• address deadlock with rolling file appender ( https://issues.apache.org/jira/browse/LOG4NET-583 )
• performance improvement for platforms not supporting WindowsIdentity ( https://issues.apache.org/jira/browse/LOG4NET-652 )
• allow using the netstandard2.0 libraries from within asp.net on net472 ( #76 )
• update to the log4j-alike output ( #18 )

Should resolve issues with PlatformNotSupported exceptions raised on !win32 when attempting to include the current user name in logs.

• corrects assembly versioning still reported as 2.0.9 in the 2.0.10 release
• ensures that stream writers used during log flushing are properly disposed
• corrects version strings for client profile assemblies

Apache log4net 2.0.10 improves netstandard2.0 support thanks to community member @NicholasNoise .

Bug Fixes

• [LOG4NET-575] Addresses CVE-2018-1285 by cherry-picking the fix from Dominik Psenner, reported by Karthik Balasundaram, as it already existed in the the develop branch