3 ms·
This, so much. My first deep dive into it I ended up in async hell. Definitely start one call at a time in a small corner of a small application. Once you unde
by jermaustin1 10y ago
This, so much. My first deep dive into it I ended up in async hell.
Definitely start one call at a time in a small corner of a small application. Once you understand async Task Method() vs async Task<Result> Method(), then how the async methods all chain back together, you can expand it.
- maxxxxx 10y agoThe funny thing is you can use async successfully without having a clue. But one day it will bite you hard.
- naasking 10y agoThis is really a problem for .NET itself. The pervasive availability of thread-static state is the only way async/await could really go wrong.
- maxxxxx 10y agoThere is more that can go wrong. For example in a desktop app a button click finishes before the async code has been executed. The code looks like it's blocking but it isn't. I have seen that a few times now.