I would say that since you want to wrap the Logging Application Block then you must have some requirements in mind on what API you want to expose through your wrapper. So, in that sense, how you wrap the block is up to you. If you are intent on wrapping
the block then, as I mentioned, I would recommend using Common.Logging (you can read about it
) since it will let you switch between different logging approaches (NLog, log4net, etc.) without changing any code and save you from. (Usually, that is one major reason for wrapping a logging implementation.)
You could create your own Logger class that returned a Common.Logging.ILog instance based on configuration or some sensible defaults.
My unsolicited opinion is that logging is important but the less time you spend on it the more time you have to create the application functionality.
Enterprise Library support engineer