Do I have to await an async method?

Question

I use a HttpClient that only supports async methods. Do I have to await them in the calling method (not in the async method itself, I have to await the calls in HttpClient methods as far as I know)?

I don't really need multithreading in that project. I would be fine blocking and waiting until I get a response from HttpClient as I need to have the data anyway. This is a Console application.

check this : http://stackoverflow.com/q/14455293/3956100 – Niklas Sep 18 '16 at 23:31 — Niklas, Sep 18 '16 at 23:31
If you need a result back - you `await` for it. – zerkms Sep 18 '16 at 23:31 — zerkms, Sep 18 '16 at 23:31

Jonesopolis · Answer 1 · 2016-09-19T12:31:48.017

4

No, nothing requires you to await the call. The call is just returning a Task<T> to you, rather than a T directly. If you call the Result property on the Task:

var result = client.MakeCallAsync().Result;

You are telling it "I don't care if it blocks, I want my code (and this thread) to wait here till this is done."

edited Sep 19 '16 at 12:31

answered Sep 18 '16 at 23:39

Jonesopolis

25,034
12
68
112

score 2 · Answer 2 · answered Sep 19 '16 at 00:14

I don't really need multithreading in that project.

async is about asynchrony, not multithreading.

I would be fine blocking and waiting until I get a response from HttpClient as I need to have the data anyway. This is a Console application.

In this case, then, I'd just say to keep everything synchronous. That is, use WebClient instead of HttpClient.

Do I have to await an async method?

2 Answers2

Linked

Related