Error handling

[py-tounge]

How would you handle an error if, say the toaster burned the toast, didn't pop up, and caught fire?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 17d27a0d-c072-8c9f-7e31-3de60bee9ae8
• Version Independent ID: e0c09794-e712-19ff-cb9f-12648d60d4f6
• Content: Asynchronous programming in C#
• Content Source: docs/csharp/programming-guide/concepts/async/index.md
• Product: dotnet-csharp
• Technology: csharp-async
• GitHub Login: @BillWagner
• Microsoft Alias: wiwagn

[BillWagner]

That's a great idea @manwithoutname

How exceptions are handled in async tasks is a large enough topic that it should be its own article. I hadn't thought about extending this with error conditions, but it is a great next step.

I've added this to our backlog to address in an upcoming sprint.

[nunorelvao]

On my experience indeed this overview is good , but quite simplistic on real usage case, as mentioned by "ManWithoutName", i too think that needs to talk also about Error Handling (How Exceptions are handled (or should be), and how could you, eg: have a TASK function that is not "async" and innner code you call another that is "async" . Best practices with all possible scenarios (ERROR Handling, Task.Result vs Wait() for ex...)