C# Async/Await/Task Explained (Deep Dive)

In this tutorial we conver the asynchronous programming style in C# we take a deep diving looking at the state machine that the async keyword spawns. How the await keyword creates checkpoints in the state machine. And how the Task class allows us to bridge our code to use the asynchronous programming model.
Source: github.com/T0s...
Patreon 🤝 / raw_coding
Courses 📚 learning.raw-c...
Shop 🛒 shop.raw-codin...
Discord 💬 / discord
Twitter 📣 / anton_t0shik
Twitch 🎥 / raw_coding
👉 Try Rider
www.jetbrains....
RD5K9-4TXXW-KMV3G-NYWSF-3ZSTP
Videos
Karel Zikmund • Async demystified - Ka...
Jeffrey Richter • LTS Webinar “Performin...
Jeffrey Richter (with Demo at 41:55) • Performing Asynchronou...
Adam Krieger (Good info on Thread Pool) • Stealing Time with the...
Articles
devblogs.micro...
www.codeprojec...
ranjeet.dev/un...
#csharp #async #dotnet

[@rheinelroimanalo7321]

Thank you programming Jesus!

[@RawCoding]

Stay blessed son

[@sonikajha3788]

😂

[@dattabansode6598]

misunderstanding is extremely common. Many people are taught that multithreading and asynchrony are the same thing, but they are not. Example. You are cooking in a restaurant. An order comes in for eggs and toast. Synchronous: you cook the eggs, then you cook the toast. Asynchronous, single threaded: you start the eggs cooking and set a timer. You start the toast cooking, and set a timer. While they are both cooking, you clean the kitchen. When the timers go off you take the eggs off the heat and the toast out of the toaster and serve them. Asynchronous, multithreaded: you hire two more cooks, one to cook eggs and one to cook toast. Now you have the problem of coordinating the cooks so that they do not conflict with each other in the kitchen when sharing resources. And you have to pay them. Now does it make sense that multithreading is only one kind of asynchrony? Threading is about workers; asynchrony is about tasks. In multithreaded workflows you assign tasks to workers. In asynchronous single-threaded workflows you have a graph of tasks where some tasks depend on the results of others; as each task completes it invokes the code that schedules the next task that can run, given the results of the just-completed task. But you (hopefully) only need one worker to perform all the tasks, not one worker per task.

[@RawCoding]

Can you explain to me what made you think I'm misunderstanding something? To me it seems you explained what I explained but from a high level, which is what everyone does, and at no time did I make the following claim: > that multithreading and asynchrony are the same thing, but they are not. My explanation is based around - handing off a task to something else to work on, so in your example it would be a fryer (external process) frying an egg (working on a task), and we are not waiting for it (thread isn't blocked). When I go to explain that a different thread may complete the rest of our task it's like chef1 starting to cook an egg and chef 2 finishes it. If you are just giving another high level overview of asynchrony there are ton's of these, people are still looking for these videos because they want to understand the abstraction behind it. And I'll re-state I do think your explanation is correct and informative but doesn't cut where it needs to.

[@exogendesign4582]

Should've have find this comment sooner, I should learn both though. What I want was Synchronous for my project Since it depends on the completion of the first task before the next. that's why I there is no blocking in my app, since im using async, it really baffles me but this comment really made me see the difference, and the video made me understand how to right the code, good combination. Thanks for sharing your knowledge Datta Bansode. and Raw Coding you guys rock.

[@emreaka3965]

@@RawCoding You said, "another thread is indeed going to complete the boiling process." but the man says "there is no another thread. it runs single thread." If I am wrong, please correct.

[@user-xh1du2uw6y]

​@@emreaka3965 I think that the number of threads depends on operation type we need to execute (IO-bound or CPU-bound). IO-bound operations don't need additional threads, they use some external devices that don't need our help. But I might be wrong

[@ZombieMagnum]

As I understand it from this video, the use of async/await DOES in fact sometimes automatically create additional threads, hoewever not necessarily for every async function or await statement. It is confusing that people insist that async/await is ''single-threaded asynchrony" when in practice it is not true. I do understand that multi-threading is a different concept, your explanation is great.

[@pratikzirpe315]

I haven’t seen anyone else explain such complex concept with such ease and still thorough - to the point. Thank you 🙏🏻

[@RawCoding]

Cheers!

[@PaulSebastianM]

@@RawCoding 5:53 Cheers! 😆

[@aronhegedus]

this is really useful because you're showing us the inbetween code, rather than just telling us. I find that that's usually the most instructive, because I can then go and check that as well

[@ragtop63]

Although I already had a pretty good understanding of how all this works, I have to say that your explanation is by far the best that I’ve seen. Too many times other videos show you some simple implementation that really can’t be ported to the real complexities of asynchronous programming. So you leave those videos with a “Hmm, ok. I guess that makes sense. But how do I apply it to my specific situation?” kind of feeling. What you’ve done here is not given us the fish but instead taught us how to fish. A fundamental understanding of complex topics is always the best method. Great job!

[@TJahmusick]

This is exactly how I wanted this explained to me. Incredible! Thanks!

[@RawCoding]

Thank you for watching))

[@spuriustadius5034]

I got totally confused about Dump() and Dump(string s) until I realized that you are using some kind of built in extension method that your IDE (linqpad?) somehow defines for you. Once I understood that, it was super clear.

[@RawCoding]

Awesome! glad it didn't get in the way too much :) Yeah linqpad is like a mini development environment, as you can see I get to run my code instantly instead of waiting for the app to compile/start etc... and the data vizualisation that you get through Dump can be pretty incredible :)

[@nobytes2]

pretty weird tbh, just use console write like every other human 🙄

[@RawCoding]

No

[@Jwhite1979]

100% this! I'm 1:49 into the video, and I pull out C# In A Nutshell, find nothing, Google "String dump method", find nothing, search through KZbin comments for someone, for the love of god, anyone explaining what the hell this .Dump method is all about! Thank you Spurius. Today, you're the hero.

[@RichardONeil]

@@RawCoding agreed...Linqpad is the greatest tool on my belt to quickly work things out. You get all the cruft out of the way and can hone directly in on an algorithm that you are trying to build, or understand. I highly recommend buying it to everybody that does this for a living.

[@aleksandermirowsky7988]

Rust's async/await functionality operates in a similar way, as it also expands into a state machine. It has been explained by Rust experts multiple times, but your explanation takes it to another level. The ability to visualize the intermediate generated code is just the icing on the cake. Great stuff, happy to see that you're still an actively posting on KZbin. Instantly subscribed and activated notifications.

[@RawCoding]

Thank you really appreciate it!

[@hsnnoznn]

Man, I usually take the information I need and close the video but you are absolute legend. I can not skip without a huge thanks. You explained it very well. Again, thanks a lot.

[@user-yc9rp8mv5b]

Dear friend. Visit youtube channel "Solve My Programming Task". They create simple programs for free. I used it. I am a student.

[@mikecu2249]

This must be the Best Explanation about this Topic on our Planet! You didnt not only manage to create a crystal clear image, approch and explanation. You also picked the confused C# Devs up who still tried to figure out, what the clock is happening to my code? Thank you!

[@RawCoding]

Glad I could help!

[@MiningMozo]

Step 1 - Complete High school Step 2 - Complete Colleges The next step is to figure out what the fuck is going on

[@RawCoding]

Pretty much :P

[@michalbrndiar5317]

Crystal clear and absolutely the best explanation of this concept I've ever seen. Keep up great work! :)

[@RawCoding]

Thank you )

[@WantOxide]

Bullshit this crap is not clear

[@michalbrndiar5317]

Hmm, probably it is not this video's fault. 🤔

[@WantOxide]

@@michalbrndiar5317 of course it is. there are more clear videos, so it's clearly his video fault

[@WantOxide]

@@michalbrndiar5317 And if it's not his video's fault it means you just do spaghetti code as he does (and spaghetti explanations)

[@speakoutloud7293]

Man, I just can't get enough of your videos. You rock with this! Keep it up.

[@RawCoding]

Cheers, glad you liked them

[@pieDesert]

S-Tier explanation and demonstration. It is so difficult to find decent tutorials out there, but this one was no fat just cut right to the information I needed to hear and delivered with such simplicity. Also actually using the full time of the video to teach and explain and not self promote and advertise. Appreciate the raw commentary!

[@RawCoding]

Glad I could help)

[@emrealtuntas1319]

After 05:51 i directly clicked like button.

[@RawCoding]

Hehe

[@nipungrover7058]

Legend has it that you understand programming better when jesus teaches you himself. Amen.

[@Esurnir]

Thank you for clearing up this absolute swamp of complexity that is async await in c#

[@RawCoding]

Thank you for watching))

[@cuzsleepisthecousinofdeath]

Finally a person who's just like Jamie King(pardon me for making a comparison): straight to the point, showing the internal guts of things Subscribed instantly

[@RawCoding]

Cheers

[@StreetBladerBloke]

Very clear and especially deep dive which is always a missing part in programming videos, you have nailed it.. thanks and keep it up with these videos they are pure gold..maybe u can create a course and sell it..I am sure deep dives are missing in today's programming world where instructors are just bothered about creame only but not the cake. You and Jamie king are the only ones who are taking it to another level. Thanks for ur efforts

[@RawCoding]

Cheers, there will be a course at one point

[@LarrySmith1437]

Well done, sir. I struggled with how to present this topic to my dev department, your example helped a lot.

[@RawCoding]

Cheers

[@TheFeaz]

Hey man, this (and your other video showing HOW to use async / await) was REALLY good information. Another person said it, but I'll say it again, this was the best presentation of this material that I've ever seen. I'm a senior software engineer with my company, and I've been here almost 20 years. Most of my work is in hard-core business logic, and I haven't done a lot with system-level stuff, multi-threading, and all that. With the changing system model these days and an emphasis on micro-services, I'm re-visiting these concepts (that and I'm doing some of my own private consulting now, doing web development, Docker containers, etc. and certainly am seeing a lot of this async stuff, particularly in the bakc-channel OAuth stuff.) Anyway, the biggest challenge I have learning this stuff in a meaningful way is that content out here usually goes one of two places-- It either shows very simplistic "hello world" type examples, that make would make a great "Await / Async 101" course or a college lab project, but in practice they don't scale well to anything resembling what we would actually DO in an enterprise application. On the other hand, there are task-oriented "how-to's" that show you the how but not the WHY. I really appreciated your deep-dive into this and a look at how the MSIIL implements this. That really gave a whole new dimension to my understanding of how this stuff actually works under the covers, and gives me some much-needed insight into how I could leverage these features in our enterprise applications.

[@RawCoding]

Thank you for your comment))

[@jasonherrera7605]

Thank you, it is difficult for me to follow your English, but it has been the best explanation I have ever known.

[@RawCoding]

Awesome, thank you )

[@magerehenk7579]

why is it difficult to follow his english?

[@RawCoding]

I’m not a native speaker and some other people aren’t ether, so it’s a compounding effect

[@ehsanhadid1260]

Just wow, I want to go back, leave University and just follow you.

[@RawCoding]

Haha don’t do that :P

[@investmentjourney7912]

Best explanation till now, not just showing windows form for ui activeness like others. 👍

[@RawCoding]

Cheers

[@lefrutit228]

tutorials such that are exaclty what youtube needs lol, I barely can find tutorials that I cant understand from the first watching, they're too simple, but this is excellent, thank you!!

[@RawCoding]

Thank you 🙏

[@geerivana]

Your videos are way better than any other official online courses

[@RawCoding]

Cheers

[@forbin80]

Bruhhhh... I've been reading about and even using async for a couple years now and in 20 mins you just cleared up everything I didn't understand about the way this stuff works. All the weirdness I've seen in my code now makes perfect sense. Fantastic video, I can't thank you enough. By far the most clear explanation of async/await I've ever seen.

[@RawCoding]

Thank you, glad I could help:)

[@zhh174]

thank you so much. no one explained it on youtube. they just show the use of async and await.

[@RawCoding]

Cheers, that’s what my problem with all the tutorials were :)

[@razortier4284]

Great job. Not so many guys are explaining how it works under the hood with state machine

[@gotham4u]

Wow, I understood it finally . I was trying to understand async and await keywords for last an hour, but "yield" was not comprehensible. Thanks very much.

[@RawCoding]

Cheers, I have a video about IEnumerable and yield you can have a look

[@rafiul41]

One of the most underrated channels on KZbin.

[@Time_Leak]

Thanks for the clear explanation. It was really helpful to see IL that is responsible for all the magic.

[@RawCoding]

Cheers)

[@hlazunov]

This is the insane video about async/await in .NET. I have never seen a better explanation of async in .NET. Thanks a lot.

[@AjitGoel]

This is a amazing video, first clear explanation of the async-await internals. Thank you Raw Coding.

[@RawCoding]

Thank you for watching

[@rmcgraw7943]

I have a good idea for a video…Consider this…you have a UI, a service layer, a business layer, a data services layer, and a data store layer. Should you, or would you, have async methods that awaited each subsequent layer, or would you have a UI layer that had async methods/controllers (so you could await calls to the service layer and/or business layer), and would those subsequent down tier calls also be LABELed as async methods, themselves having calls to deeper layers that it awaited…OR, would you have async UI Methods that awaited down tier(business layer) calls to methods (that were not LABELed async [the keyword]) that simply returned Task. That is to ask, would you chain down tiers like Async UI awaits Async Service that awaits aync Business that awaits async Data, etc, or would you have Async (to enabled await) UI that awaited Task returning Service that called Task returning Business, etc? TRUST ME, it MATTERS ALOT! The labeling of methods as async that have no await in them has a non-negligible cost in context switching and state persistence, not to mention the garbage collection involved in cleaning all those state machine allocations.

[@marketfinds]

Excellent work, glad you went down into the IL Code. Helps make it clearer what magic is going on.

[@RawCoding]

Glad you liked it!

[@kopilkaiser8991]

Thank you so much for taking the time to explain it. I have understood some of the concepts and I will need to rewatch it to better grasp the concepts. But still I was completely lost with this asynchronous programming, and was able to find some of the way by watching your tutorial. Thank you for simplifying the complex concepts. It takes a great mind to decode the entanglement which the async await Task brings in when you jump into it after being comfortable with synchronous programming. I will keep on digging into this until it is drilled deep into my mind.

[@user-yc9rp8mv5b]

Dear friend. Visit youtube channel "Solve My Programming Task". They create simple programs for free. I used it. I am a student.

[@martinrogachevsky5627]

One of the best explanations so far, great examples, thanks a lot! Only one thing didn't let me go through this on the first attempt is when you were explaining what network device is doing with the thread on your 'art', you said that it "frees" the thread. For someone who is not native speaker that sounded a lot like "freeze" the thread and really confused me for some time. So just be aware of these little verbal things but in general very helpful and worth sharing!

[@RawCoding]

Thank you, yeah I’m not a native speaker so might mess up some pronouncements

[@ghazanfarabbas4187]

Never seen such a insightful video before. Keep it up man...

[@RawCoding]

Thanks

[@_Ming_Ming_]

Thank you for this clear explaination sir! for this I will never skip ads in your video

[@RawCoding]

thank you

[@abhirammadhu2973]

You didn't add sugar😒 BTW, this is the best video explaining async/await in C#. You're right. All other video just simply explains how to implement asynchronous program rather than explaining what exactly happens under the hood.

[@RawCoding]

thank you

[@dunefedaykiin]

Awesome video, like always! Looking forward to the next video about the practical use of async/await!

[@RawCoding]

Cheers ))

[@iedi3]

very impressive quality, and the relaxed atmosphere just perfect for some cigarettes and a beer (even though i stopped both), plus a reggae music in the background

[@phongs2nhu]

Good job, man. I'm from Viet Nam. So by watching your video, I studied new knowledge and English language. Of course, your voice is great with nice intensity. Thanks a million.

[@RawCoding]

Glad I could help :)

[@armandopenaleonett1258]

Thank you I have always had problems understanding this now it's way more clear!

[@RawCoding]

Awesome 👏

[@oganovdavid]

Thanks so much for sharing your knowledge. Haven't met anyone explaining this better than you. I've finally got some understanding of what's going on. Subscribed

[@RawCoding]

Cheers, glad I could help :)

[@Hypermommy]

Thank you for this very clear explanation of a sometimes confusing concept.

[@RawCoding]

Thank you for watching

[@stevenstone307]

Awesome explanation mate. Funnily enough another thing I learnt in this video is that you can put underscores in big numbers lol

[@RawCoding]

Double whammy!

[@xieweiling7543]

The last part - the state machine is interesting!

[@RawCoding]

sure is!

[@vaya99]

Best explanation for async await 👍, looking for deep dive for .ConfigureAwait() function. Keep it up ... how my computer is expecting it and how to read a code sequence is best part with respect to state sequence explanation.

[@RawCoding]

Glad I could help )

[@rowanlidbury]

How have I not found you before.? You need to investigate why you don't show up cos this is gold.

[@RawCoding]

Thank you)

[@user-qy4zo8qn4i]

Awesome video! Just what I was looking for. Also while I was diving into the Task code I had noticed a TaskStatus enum at the top. Immediately I was thinking that there must be some state machine at work happening here. So thanks for confirming that.

[@owiz9212]

Thanks very much Anton! Really simplifies asynchronous processing. Much appreciated!!

[@RawCoding]

Thank you for watching

[@kasra7885]

You left no questions. And a good rhythm

[@RawCoding]

That’s what we like :D

[@sreekanthbharatham7577]

Simple and very useful explanation of context switching. Never seen anyone put it together like this. For a long time I was aware the await takes control back to caller making it do other stuff. But never could grasp how potentially another thread picks up the context to continue from where it left off. That realization and looking at different thread ids in different blocks made a world of difference in my understanding. Simply outstanding !! Thank you

[@RawCoding]

Glad I could help:)

[@martinnicolas1399]

Finally, I understand what is happening! Thanks

[@RawCoding]

That is awesome

[@anpham871]

Thanks a lot!! You motivated me so much!! You are the best C# developer i've ever seen on youtube.

[@RawCoding]

Cheers ma dud ))

[@BryantCobarrubias]

You're a very good teacher.

[@RawCoding]

Thank you

[@elkhoukhi]

Man I just came across your channel, quality material! I subscribed, Keep up the good work

[@RawCoding]

Thank you, hope you like the rest :)

[@BradenJohnYoung]

Finally, a good freaking explanation. Thank you!

[@onnuttig]

Finally just a simple example of how this shit works, thanks man, instant sub

[@RawCoding]

Glad you like it )

[@mrwillis5339]

Useful to hear a concise explanation .

[@RawCoding]

Glad I could help

[@jimsteinPeerless]

You do overemphasize the importance of threads like everyone trying to explain Async does. It is a nice very demo but (this is not covered by this video) if you in the first example replace the await Task.Delay(300) with a busy loop (the same as in the main function) there will not be another thread spawn and everything will execute on a single Thread. This is task concurrency on a single thread(?). Task.Delay is not CPU bound but the busy loop is CPU bound. So Task.Delay is good for simulating an IO bound Task and therefore you get continuation on another thread. The threads are operating on a layer below concurrency, so you do not need to have multiple threads to have Task concurrency(?). Kind regards

[@RawCoding]

Thank you for sharing

[@mrcalico7091]

@@RawCoding Thankfully, You're the teacher here!

[@matthewkeron1448]

schooooled him

[@user-hp9zq3jn7s]

Can someone please explain me what Jimstein Peerless meant? As he said, i replaced "await Task.Delay(300)" with CPU bounded task (the loop shown in the video for example): await Task.Run(() => { var a = 0; for (int i = 0; i < 100_000_000; i++) { a += i; } Console.WriteLine("CPU-bound task in running on ThreadId = " + Thread.CurrentThread.ManagedThreadId); }); And i still see it being executed on another thread (Console.WriteLine shows thread id different from the main thread id). OR did he meant not using async/await and just start a raw CPU bound loop? But then it would be totally synchronous program and it is not the point of this video. But he still got so many likes on his comment. So seems like people found it useful. I am so confused...

[@RawCoding]

I guess I haven’t explained the Task.Run in this video where it’s literally a task you give the thread pool to execute, if you have a Synchronous Task method that returns a task without having async await , it will literally wait for the function to finish executing to give you the result of a Task object, like a normal function you are just waiting for the return value.

[@StevenBloomfield]

Always wondered what all the MoveNext calls were in aggregate exception stack traces. I see now where they come from. Thanks!

[@RawCoding]

Glad I could help

[@BorisMiljkovic]

Finally, a good explanation. Thank you!

[@RawCoding]

Glad you enjoyed it!

[@tomaszwitkowski9545]

I am in the fifth minute and I got understood it more than I had understood after the classes

[@RawCoding]

Hope you find the rest just as useful)

[@ehsaneftekhari4525]

Thanks a lot. that was the best explanation of how async actually works 🙇‍♂🙇‍♂🙇‍♂🙇‍♂🙇‍♂. now, I can sleep

[@ievheniiierokhin1677]

Good way to explore what really happens behind the scene with ilspy

[@RawCoding]

Cheers

[@ldohlj1]

Wow! Great analogy and great explanation. Thank you

[@RawCoding]

Thank you for watching

[@dishantchourasia4513]

Awesome explanation! Please keep up the good work

[@AC-fs2rl]

This is the thing I was looking for, thank you

[@RawCoding]

Glad I could help!

[@stardrake691]

Awesome explanation, I’ve always thought that async-await in C# acts like the one in Javascript, but there are differences.

[@thatguywiththeface9463]

Very detailed and well explained tutorial. Thank you, coding Jesus!

[@RawCoding]

Haha thank you

[@matthewsheeran]

Very good explanation. I too am going to look with ILSpy to see the non-async code which is generated which helps to see the calls to turn async code back into sync! ;-) So basically asyc/await does nothing more or less than build the state machine for you on your behalf. Also its async/await all the way up and down.

[@RawCoding]

Yes )

[@rajenlenka7806]

God bless you ..May you live a 100 years

[@RawCoding]

Thank my brother

[@MetaArcher]

Pretty cool and clear video. One of the best async videos I've seen. Hope next time you do a deep dive to compare Parallelism and Async

[@RawCoding]

Thanks, as I’ve shown in this video it’s pretty much parallel already )

[@user-li9jq7iw6r]

Best explanation i've ever seen. Thanks!

[@RawCoding]

Ty

[@koenfrontatie]

really appreciate your style of teaching! you've helped me lots

[@sankaralingammuthusamy6142]

It was really superb explanation about async and await. Thanks bro keep up the good work

[@Voloshhka]

Literally turned on this video while making a cup of tea😅

[@kadirfurkancaybas580]

The best explanation ever.

[@loam]

23:36 Second second, heh, nice language metamorphosis, I noticed that thing myself couple weeks ago while ruminating in English, and now It pop ups in the video)

[@RawCoding]

hehe )

[@CCV334]

Love the explanation! Would love to see a video on the basics of LINQPad. I can intuit how Dump(); works but would love to see your take on what's possible with the software.

[@RawCoding]

Linkpad has a tutorial built in that does it

[@tylergoffinet1085]

Great personifications and IL code walkthroughs! Thanks!

[@RawCoding]

Cheers

[@user-yt8cf6zw1i]

Wonderful explanation!

[@RawCoding]

thank you

[@lucaspedroso3351]

Man, thank you for making it simple

[@RawCoding]

Thank you for watching)

[@arunkutube]

love it, thanks for explaining using ILSpy, it makes things clear.

[@RawCoding]

Glad you like it

[@yv989c]

Continuation if the word you are looking for 🙂. Great video.

[@RawCoding]

Cheers )

[@emmanuelmotsi]

Such a great explanation. Learn a lot from the DEEP DIVE! Thanks!

[@jwange1]

Oh man! you really have a good head in clarifying things. thank you. Besides, what kind of editor do you use? interesting!

[@RawCoding]

Rider and LinqPad

[@alexplom5958]

Absolutely phenomenal video

[@RawCoding]

Cheers)

[@abuzeromohammed3386]

You hit important topics thanks

[@RawCoding]

Thank you )

[@rafaspimenta]

I really love to see how debug threads and async codes to find bugs in parallel tasks

[@KrishnaList]

Very Nice Explanation Anton It is really Deep Dive

[@RawCoding]

Thanks )

[@tweakmy]

I was looking good material for async and I didn't have time to sit on other material. Yours is the best to understand within minutes.

[@RawCoding]

Awesome!

[@antropovp]

My favorite .NET youtuber

[@noxagonal]

Small summary for C++ people. Functionality vise "Task" is very similar to "std::future". "async" is similar to "std::async" except that the function itself is defined asynchronous instead of calling any function asynchronously. To get the same behaviour in C++ as in C# you could make a function that calls another function with "std::async" and returns "std::future" Implementation vise they're of course very different.

[@drillerboyyt4027]

I am so happy I found his channel.

[@COLAMAroro]

Really nice tutorial ! Easy to understand, goes into detail and cuts when there are silence, so the video doesn't get too long Quick tips, on LINQPad, you have `Util.OpenILSpy()` built-in, no need to build a project on the side to see what's inside 😉

[@RawCoding]

Thank you!!

[@TheJAGreaper]

I think the part you mentioned about the task executing on another thread is not technically correct especially considering the lack of the use of .ConfigureAwait(false). The whole concept of multi-threaded programming is entirely separate to the async programming model being that the async programming model is an abstraction for parallelism. It could be running on another thread, it might not, the default behaviour of the synchronisation context will resume the task on the same thread unless .ConfigureAwait(false) is specified. The exception to the rule, of course, being ASP.NET Core which uses a thread pool instead of the default behaviour of the synchronisation context.

[@RawCoding]

I don’t say the task is ran on another thread, the task may be completed by a different thread.

[@TheJAGreaper]

@@RawCoding 7:00 - 7:05

[@RawCoding]

I see, yes you are correct, I’ve said it runs in parallel, which is not 100% correct, it runs synchronously up until await and then goes in to the big loop and a different thread completes the task. So there is a degree of parallelism but isn’t ran in parallel

[@TheJAGreaper]

​@@RawCoding Well no a different thread doesn't necessarily complete your task in parallel because you haven't told the synchronisation context to allow the task to run somewhere other than the captured context with .ConfigureAwait(false), Thus if the current synchronisation context only has access to one thread the exact same thread executes the code when it is freed up by the await call you to make with the Task.Delay method. This is especially dangerous when you are working with STAThread frameworks like WPF because the SyncronisationContext for the UI thread only has access to the UI thread making it incredibly easy to create deadlocks when working with WPF if you're not using .ConfigureAwait(false). (You can read more about it here from Microsoft themselves devblogs.microsoft.com/dotnet/configureawait-faq/ ) Asynchronous programming with tasks can be parallel and they can be multi-threaded but they are no inherently so, what they are is an abstraction for thread management, not parallelism and multi-threading. You can have an entire application the uses async programming but only ever has one thread (not that you would want that). So when you explain it as if it is based around threading and parallelism you are passing on a very dangerous misunderstanding that will bite developers in the ass when they encounter these cases.

[@RawCoding]

I know it doesn’t necessarily complete the task, the example that I showed in the video I specifically show that the thread is working in the loop while the task completes. The exception is a WPF app where there is a UI thread that you need to sync with. Also thank you for sharing the valuable information.