[Question]Current Status of .ConfigureAwait(false)? #9545
Unanswered
tzengshinfu
asked this question in
Q&A
Replies: 1 comment
-
There was no update recently. I'm also supporting this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, folks:
Currently, our team is using .NET Framework 4.8.
We have two C# libraries, one for accessing the databases and the other for interacting with the PLCs.
The server-side console project references these two libraries,
while the client-side Windows Forms project communicates with the server via Web API.
I’ve been away from C# for a while (was in the Java ecosystem, recently reassigned back to C#).
From what I remember, it was recommended to use .ConfigureAwait(false) in common libraries, right?
However, after being away for so long, seeing a bunch of .ConfigureAwait(false) calls still feels visually distracting:
(Also, asynchronous method names are usually in the form of Get/SetXXXAsync, which is clear—but sometimes really too verbose.)
Has this situation improved nowadays?
Beta Was this translation helpful? Give feedback.
All reactions