That's an interesting point. Would you mind to share your thoughts and
reasons why you picked log4net over other logging frameworks beyond
being a log4j port?
On 2016-09-20 01:30, Nicholas Duane wrote:
I can understand the breaking changes thing, but my impression is that
straying from the
Maybe a bit of history would help.
We had written our own logging framework a while back, prior to the launch of
.NET. It was a Windows only framework which under the covers used ETW (Event
Trace for Windows), a very high performance logging mechanism which is used by
the Windows kernel and
