The main advantage is that it is intended for libraries, to make sure everyone can use their own logging with it, without having to use different logging frameworks chosen by each library. It also has built in support to detect if some popular frameworks are present, to use those.
As an example, I have chosen Serilog in the Tests project to demonstrage how it looks to a consumer. Totally transparent, a consumer would use his logging framework as he usually does, and knx.net plugs into their choice.
I have added the LibLog Nuget package for logging. This is a source-only package, so it does not force any dependencies on anyone using knx.net
You can find more info on it here: https://github.com/damianh/LibLog
The main advantage is that it is intended for libraries, to make sure everyone can use their own logging with it, without having to use different logging frameworks chosen by each library. It also has built in support to detect if some popular frameworks are present, to use those.
A good explanation can be found at https://cmatskas.com/application-logging-with-liblog/
As an example, I have chosen Serilog in the Tests project to demonstrage how it looks to a consumer. Totally transparent, a consumer would use his logging framework as he usually does, and knx.net plugs into their choice.