Overriding the OnUnhandledException doesn't seem to work for exceptions raised from within spawned threads.
I verified this by raising an exception from the UI thread. That is caught as expected. Any workarounds that do not require me to change my application structure?
Comments: The OnUnhandledException function is only called when an exception is raised on the dispatcher, since it hooks the event ```C# Application.DispatcherUnhandledException ``` In case of exceptions raised in tasks, other threads, or generally outside of the dispatcher, OnUnhandledException is not called. It is up to you to handle such exceptions, and act as needed. Mostly, AppDomain and unobserved Task exceptions are enough, so in the Bootstrapper ctor (or static ctor), you can hook these events: ```C# AppDomain.CurrentDomain.UnhandledException += OnCurrentDomainUnhandledException; TaskScheduler.UnobservedTaskException += OnTaskSchedulerUnobservedTaskException; ```
I verified this by raising an exception from the UI thread. That is caught as expected. Any workarounds that do not require me to change my application structure?
Comments: The OnUnhandledException function is only called when an exception is raised on the dispatcher, since it hooks the event ```C# Application.DispatcherUnhandledException ``` In case of exceptions raised in tasks, other threads, or generally outside of the dispatcher, OnUnhandledException is not called. It is up to you to handle such exceptions, and act as needed. Mostly, AppDomain and unobserved Task exceptions are enough, so in the Bootstrapper ctor (or static ctor), you can hook these events: ```C# AppDomain.CurrentDomain.UnhandledException += OnCurrentDomainUnhandledException; TaskScheduler.UnobservedTaskException += OnTaskSchedulerUnobservedTaskException; ```