Question

I wanted to know if you suggest (in your opinion) using / building a logger wrapper such as Common.Logging in order to use some kind of logger?
I presume that the use of such wrapper is to :
1. Enable changing the logger library when needed.
2. Make the API easier.
In the end does it really matters ? or the loggers are easy to use and do not need to simplify it or change the logger just like that.
Thanks.

Answer 1

I have written a wrapper logging library that uses health monitoring for asp.net sites and log4net for windows/console apps. This way the logging interface always stays the same and is easy to be used enterprise wide. In our case, we only wanted to log a few categories, error/debug/info etc. If you think you need to use some special features of a specific logging library, you may choose to implement it directly. If you are using any third party logging libraries, it may be good to have a wrapper because what if the support for that is stopped or you need to move to a better one later.

The decisions are always almost dependent on your specific needs and future plans.