What should I do with the global exception?

Whether there is a mechanism like wfp’s DispatcherUnhandledException, my logic is that Project A refers to Project B, project B throws an exception, but not fatally just a hint. I want the program to continue running instead of exiting the program.

//when exception was throw
private void App_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e)
{
    if (e.Exception is UserFriendlyException)
    {
        e.Handled = true;
        Log.Logger.Error(e.Exception.Message);
        MessageBox(e.Exception.Message);
        //Other logic...
    }
    //Other logic...
}

Any suggestions or best practices？

I still don’t find useful information through search engines, which is the only relevant introduction I’ve found so far, but I don’t quite understand how to use this https://gitter.im/AvaloniaUI/Avalonia?at=5d833ca2a7a5cc473319c6ed https://www.reactiveui.net/docs/handbook/default-exception-handler/

[worldbeater]

RxApp.DefaultExceptionHandler allows you to catch any exceptions thrown from a ReactiveCommand, ObservableAsPropertyHelper, and other stuff. It is recommended that in an Avalonia.ReactiveUI app you wrap the code that might throw exceptions into reactive commands (ReactiveUI ICommand implementation), see https://www.reactiveui.net/docs/handbook/commands/ This way your exceptions will tick through your RxApp.DefaultExceptionHandler and won’t cause the crash of your app.

// Here we subscribe to ReactiveUI default exception handler to avoid app
// termination in case if we do something wrong in our view models. See:
// https://www.reactiveui.net/docs/handbook/default-exception-handler/
//
// In case if you are using another MV* framework, please refer to its 
// documentation explaining global exception handling.
RxApp.DefaultExceptionHandler = Observer.Create<Exception>(Console.WriteLine);

[maxkatz6]

@olgaMuravjova since DispatcherUnhandledException or any other global unhandled exception handling, which prevents app from crashing, (and most possibly being trapped in invalid state) is considered as a bad practice, we don’t really plan to support it.

If you want to handle global errors, you can catch them in Program.Main method, log and close the app peacefully (restart or open report-error app if needed). Any other expected errors should be handled explicitly in place where they are expected.

Alternatively, as it was mentioned above, if you are using ReactiveUI with your app, this library actually provides DefaultExceptionHandler for exceptions inside of observables. Though in most cases it means that Observable pipeline now in error state and won’t work anymore.