Missing info on support and AsyncWrapper need about nlog.targets.syslog HOT 2 CLOSED

Thanks for the answer! It all makes sense, and this is still my favorite syslog library. =)

from nlog.targets.syslog.

Sorry that you are finding these issues.

Using semantic versioning, I increased the major version to indicate there were breaking changes and I used GitHub features for release notes

Not having a persistent 2.x branch should suggest version 2 is no more supported, anyway I will try to make the readme more explicit.

As for the test application, it is meant to test multiple scenarios, therefore a complex app.config is needed: a much simpler configuration file example is in the readme, but I will try to show some more sample configurations.

With regards to the AsyncWrapper it is not suited for what the Syslog target needs and I will make it clear in the readme. Being asynchronous is usually an advantage, but to allow more control we should have a totally async implementation of NLog so that you could wait on a logging call when needing sync operations. The need for async arose when an issue was opened asking for persistent TCP or UDP connections to avoid slowing down the caller.
Async tasks should be canceled as soon as the target is disposed: if you have a console app and your main method doesn't wait for user input that's maybe the reason why you need to sleep.

from nlog.targets.syslog.