> Currently, we sprinkle `LogManager.GetCurrentClassLogger()` all over the code base and, thus, spread a direct dependency to NLog all over the solution. As was discussed in chat several times, we should probably take a nore structurised approach to this.
One concern in the past was that when deriving from a type `GetCurrentClassLogger` in the base gets the logger with the message setup for the base class. However, this can be circumvented using `LogManager.GetLogger(GetType()FullName)`.
U