GetAwaiter（）。GetResult（）与GetAwaiter（）？

Question

Most devs are using GetAwaiter().GetResult() , and I can barely dig up examples using it with without the GetResult() part, however it is illogical to use GetResult() when we don't need the result.

Is there a reason why not just use GetAwaiter() when applicable? Or is my perception of what the common usage is wrong?

Answer 1

GetAwaiter() not waits for task, just returns TaskAwater object, which can be used to wait for task by calling GetResult() . So calling GetAwaiter() only is meaningless. As documentation states this class is only intended of compiler use and users should not use it. You should use Task.Wait() , when you want to wait for task, but not need result. But sometimes users still use Task.GetAwaiter().GetResult(), Instead of Task.Wait() in try-catch block because Task.GetAwaiter().GetResult() not wraps Exception thrown while executing task in AggregateException and also shows more detailed stack trace, that makes exception handling easier.