Thursday
Workshop
09:00 - 10:00
(UTC+10)
Talk (60 min)
Part I: Understanding async machinery down to a single detail
We all use asynchronous code and we have some understanding of the machinery behind it. It's time to see how it works and learn why it's hard to synchronously wait for asynchronous code, how to wait for async void methods, or how to debug deadlocks. We will see the code generated by the compiler, understand synchronization contexts and integration with TPL library, reimplement part of the mechanism to fix deadlocks, or just play with internals to understand them better.
Objectives:
- Understanding async state machine
- Learning about synchronization contexts and how they differ between console, ASP .NET, ASP .NET Core, or desktop applications
- Implementing custom primitives for better code control
- Awaiting async void methods
- Capturing all out-of-band exceptions
- Implementing custom tasks or synchronization contexts
Requirements:
- Windows 10 running on x86_64 architecture
- Visual Studio 2019
- .NET 6
- .NET Framework 4.8
- dnSpy
- WinDBG + configured symbols + configured SOS for all .NET environments
- git
Adam Furmanek
I am Adam Furmanek, and I am a professional software engineer with over a decade of experience. In my career, I worked with all layers of the software engineering and multiple types of applications, including logistics, e-commerce, machine learning, data analysis, and database management. I am always interested in digging deeper, exploring machine code, and going through implementation details to better understand the internals of the technologies I use every day. That's why I like debugging, decompiling and disassembling the code to understand memory models, concurrency problems and other details hidden deeply inside. In my free time, I play ping-pong, watch Woody Allen's movies and blog stuff at http://blog.adamfurmanek.pl