Book Image

Mastering C# Concurrency

Book Image

Mastering C# Concurrency

Overview of this book

Starting with the traditional approach to concurrency, you will learn how to write multithreaded concurrent programs and compose ways that won't require locking. You will explore the concepts of parallelism granularity, and fine-grained and coarse-grained parallel tasks by choosing a concurrent program structure and parallelizing the workload optimally. You will also learn how to use task parallel library, cancellations, timeouts, and how to handle errors. You will know how to choose the appropriate data structure for a specific parallel algorithm to achieve scalability and performance. Further, you'll learn about server scalability, asynchronous I/O, and thread pools, and write responsive traditional Windows and Windows Store applications. By the end of the book, you will be able to diagnose and resolve typical problems that could happen in multithreaded applications.
Table of Contents (17 chapters)
Mastering C# Concurrency
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Debugging


Debugging as a very extensive topic and there are several books about debugging .NET applications techniques. Here we will review how we can start debugging with Visual Studio, and what tools can help us to debug concurrent applications.

Just my code setting

There is a very important setting located in the Debug, Options and Settings… menu called Enable Just My Code:

When this setting is enabled, Visual Studio tries to hide additional information such as compiler-generated code and does not show this in debugging windows, concentrating only on the information related to your code. This seems comfortable, but do not forget that you can always turn it off and study the whole picture in case you need to dig into the infrastructure code.

Call stack window

One of the easiest debugging tools in Visual Studio is the call stack window. An asynchronous method call usually consists of two parts—begin and end operation. If you have a breakpoint inside an asynchronous method body, it is not easy...