In this chapter, we have seen the implementation details of traditional Windows application UIs that are usually hidden by the programming platform and high-level UI frameworks. We have learned about what the UI thread and message loop are, and why they are very important to keep the UI thread running and not blocking it with long-running code. Then we learned about the common problems of asynchrony in the UI, and how to avoid deadlocks and multithreaded access to the UI controls' exceptions.

One of the most important topics covered in this chapter was the C# asynchronous infrastructure internals, showing how the await statement works, and how we can improve application performance by choosing not to keep the current synchronization context.

In the next chapter, we will look at troubleshooting concurrent programs in greater detail. We will know about many exciting features of Visual Studio for profiling and debugging parallel programs and find out how to catch more errors in the development...