C# Deconstructed answers a seemingly simply Just what is going on, exactly, when you run C# code on the .NET Framework? To answer this question we will dig ever deeper into the structure of the C# language and the onion-skin abstraction layers of the .NET Framework that underpins it. We’ll follow the execution thread downwards, first to MSIL (Microsoft Intermediate Language) then down through just-in-time compilation into Machine Code before finally seeing the results executed at the hardware level. The aim of this deep-dive is to provide you with a much more rounded knowledge of the environment within which you code exists. As a managed language, it’s best-practice to let the Framework deal with device interaction but you’ll find the experience of taking the cover off once in a while a very rewarding one that will greatly enrich your appreciate of the C# language and the way in which in functions.
The title was promising a lot of insight into inner workings of CLR. But it was all wrecked by poor execution. WinDBG is used extensively for "deconstructing" the CLR but no brief introduction into WinDBG is provided, instead copy/paste of steps to start debugger slips from one listing to another. The explanations are vague and short that hinders comprehension.