DNSProxy | simple DNS proxy server , which helps you to forward DNS | DNS library

I have a C# Program running as a Windows service doing some Network shenanigans I thought I had last-ditch "Log Fatal Errors" handling set up. But I've come across an edge case where the Service ends up dead but dodges those catches. :(

I believe this is caused by code throwing an Exception in the EventHandler registered to a .NET library's event.

Obviously I can (andshould!) catch the Exception in my handler, but I'd like to understand how this is avoiding my fall-back error handling, and whether I can add some even more robust fall back logging, to ensure that I have some log records to analyse similar silent bugs in future.

ServiceBase.Run(container.Resolve()); in a try ...catch in Program.Main() MyProjectWindowsService : ServiceBase is the service object with an OnStop() implmentation. NetworkChange.NetworkAvailabilityChanged += CodeThatThrows;

But when that Exception is thrown, neither OnStop() nor the try...catch trigger. I can get it in a debugger, and it doesn't seem to go anywhere .. it just ... stops.

Fuller program details below, if you want them.

How can I catch and log unhandled exceptions in Event Handlers registered to external library events?

(Also ... Is the behaviour I've described above the expected behaviour, or is there something slightly weird happening?)