[Netcommon-developer] Common.Logging and NLog

[Kenneth Xu <ke...@ho...>]

Since there were some talk about NLog and Common.Logging. I'd try to do a
summary on this topic.

1. Current adapter still works with NLog2 as good as it is with NLog1. But
it seems that many users are not aware of this. It would be helpful if there
is some documentation, e.g. Q&A on the website to explain this. Below quoted
a comment from
http://stackoverflow.com/questions/6778233/are-there-any-alternatives-to-common-logging

I still think that if the Common.Logging team want to make people use their
> project that a few updates to the website at least might be good - for
> example documenting the assembly redirect. Just because the code is stable
> and not changing, it doesn't mean the website should be static too.


2. Current NLogLogger in CommonLogging 2.0 has an major issue, the issue was
introduced when AbstractLogger was add in CommonLogging 2.0. The change
triggered a bug in NLog (http://nlog.codeplex.com/workitem/6350, please go
vote up) so that the NLog failed to detect the user stack frame for the log
messages sent from CommonLogging.

3. There was a proposed work around to problem 2 in
https://sourceforge.net/tracker/?func=detail&aid=3379373&group_id=182424&atid=901159,
but the approach suggested was a hack. The simplest workaround to this
problem is moving all the method from AbstractLogger to NLogLogger. (BTW, it
seems that there is no way for me to add any comment to that ticket)

4. I couldn't get CommonLoggingTarget working to bridge NLog messages, I
have created a bug and provided the fix:
https://sourceforge.net/tracker/?func=detail&aid=3382918&group_id=182424&atid=901156

Cheers,
Kenneth