In a recent post, we explored the basics of asynchronous code, why it’s important, and how to write it in C#. However, while it can improve your program’s overall throughput, async code is still not exempt from bugs! Writing async code makes debugging more difficult when potential deadlocks, vague error messages, and finding which task(s) are causing a bug are thrown into the mix. Luckily, Visual Studio has several new and old features compatible with managed, native, and JavaScript to help ease your frustrations with debugging async code. Let’s take a tour!

Where can I see all my program’s tasks?

When you encounter a bug in your async code, you probably want to identify all your Tasks and determine which of them are causing the error. If you’ve debugged multithreaded applications, you may be familiar with the **Threads **window. Good news, there’s also equivalent window for tasks! The **Tasks **window allows you to view all your tasks, displaying their IDs, current locations, the method originally passed into each of them, and their current statuses (active, scheduled, blocked, or deadlocked) at break time. If your program is multithreaded, this window will also display the threads running each task. This can help to identify specific threads which may also be contributing to an issue.

You can access the **Tasks **window at **Debug > Windows > Task **or by using CTRL+SHIFT+D, K.

Tasks window

How can I locate the origin of a thrown exception in my async code?

Determining a thrown exception’s original location is frustrating when debugging async code. When an exception is thrown multiple times, Visual Studio typically returns the call stack where the exception was most recently thrown via the Exception Helper. Unfortunately, this isn’t always helpful for async debugging. To fix this, we’ve implemented rethrown exceptions in 16.4. With this update, the Exception Helper displays the original call stack when an exception is rethrown. To learn more about this new feature, check out Andy Sterland’s blog post.

Rethrown exception example

Is there a way to better visualize tasks and async code flow?

For a graphical depiction of async code’s execution, Visual Studio has the **Parallel Stacks **window for threads and tasks. Improved for Visual Studio 16.6, the Parallel Stacks window for tasks (or **Parallel Tasks **window) visually displays active, awaiting, and scheduled tasks and how they relate to each other. Double-clicking an active or awaiting task shows the async call stack in the Call Stack window. To understand which thread is running a specific task, you can swap between the Parallel Threads and Parallel Tasks windows. You can do this by right-clicking and selecting **Go To Thread **in the context menu. To learn more about the new updates made to **Parallel Tasks in 16.6, **stay tuned for an upcoming blog post…

Parallel Stacks for Tasks window

Ready to use these tools to debug your async code?

Now that you have more tools in your belt to help you debug your code, share your feedback with us! Reaching out with your thoughts and feature suggestions will help us create the best async debugging experience.

#visual studio #.net #async #asynchronous #debugging and diagnostics #tips and tricks #visual studio 2019