How do you avoid sync-over-async deadlocks?
PICTURE THIS: ASYNC / PROMISE
Simple meaning
I never block on .Result or .Wait in ASP.NET request threads.
WHY — Threading instead of guessing?
Why interviewers care about Threading:
question about Threading.
trade-offs, and what you would actually do on a .NET project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1I never block on
.Result or .Wait in ASP.NET request threads.
- 2Why it exists
Prefer async all the way.
- 3If I must bridge,
ConfigureAwait and careful contexts matter on older sync contexts.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
I never block on .Result or .Wait in ASP.NET request threads. Prefer async all the way.