A good solution for await in try/catch/finally?

后端 未结 4 1709
南笙
南笙 2020-12-04 07:20

I need to call an async method in a catch block before throwing again the exception (with its stack trace) like this :

try
{
    //         


        
相关标签:
4条回答
  • 2020-12-04 07:35

    If you need to use async error handlers, I'd recommend something like this:

    Exception exception = null;
    try
    {
      ...
    }
    catch (Exception ex)
    {
      exception = ex;
    }
    
    if (exception != null)
    {
      ...
    }
    

    The problem with synchronously blocking on async code (regardless of what thread it's running on) is that you're synchronously blocking. In most scenarios, it's better to use await.

    Update: Since you need to rethrow, you can use ExceptionDispatchInfo.

    0 讨论(0)
  • 2020-12-04 07:38

    You should know that since C# 6.0, it's possible to use await in catch and finally blocks, so you could in fact do this:

    try
    {
        // Do something
    }
    catch (Exception ex)
    {
        await DoCleanupAsync();
        throw;
    }
    

    The new C# 6.0 features, including the one I just mentioned are listed here or as a video here.

    0 讨论(0)
  • 2020-12-04 07:48

    We extracted hvd's great answer to the following reusable utility class in our project:

    public static class TryWithAwaitInCatch
    {
        public static async Task ExecuteAndHandleErrorAsync(Func<Task> actionAsync,
            Func<Exception, Task<bool>> errorHandlerAsync)
        {
            ExceptionDispatchInfo capturedException = null;
            try
            {
                await actionAsync().ConfigureAwait(false);
            }
            catch (Exception ex)
            {
                capturedException = ExceptionDispatchInfo.Capture(ex);
            }
    
            if (capturedException != null)
            {
                bool needsThrow = await errorHandlerAsync(capturedException.SourceException).ConfigureAwait(false);
                if (needsThrow)
                {
                    capturedException.Throw();
                }
            }
        }
    }
    

    One would use it as follows:

        public async Task OnDoSomething()
        {
            await TryWithAwaitInCatch.ExecuteAndHandleErrorAsync(
                async () => await DoSomethingAsync(),
                async (ex) => { await ShowMessageAsync("Error: " + ex.Message); return false; }
            );
        }
    

    Feel free to improve the naming, we kept it intentionally verbose. Note that there is no need to capture the context inside the wrapper as it is already captured in the call site, hence ConfigureAwait(false).

    0 讨论(0)
  • 2020-12-04 07:49

    You can move the logic outside of the catch block and rethrow the exception after, if needed, by using ExceptionDispatchInfo.

    static async Task f()
    {
        ExceptionDispatchInfo capturedException = null;
        try
        {
            await TaskThatFails();
        }
        catch (MyException ex)
        {
            capturedException = ExceptionDispatchInfo.Capture(ex);
        }
    
        if (capturedException != null)
        {
            await ExceptionHandler();
    
            capturedException.Throw();
        }
    }
    

    This way, when the caller inspects the exception's StackTrace property, it still records where inside TaskThatFails it was thrown.

    0 讨论(0)
提交回复
热议问题