3 ms·
I was in the same position but I would recommend you start using it. Make sure you start with a small project and really step through each line so you can predi
by maxxxxx 10y ago
I was in the same position but I would recommend you start using it. Make sure you start with a small project and really step through each line so you can predict what will run in which thread. I notice that some people use async/await but don't really understand it which can cause problems in some situations.
It definitely makes life much easier. Can't wait to use it in JavaScript.
- jermaustin1 10y agoThis, 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.