On C # CLR execution module

Buy this CLR via C # has been a few days, but has not seriously turned over the book, previously learned the knowledge points have forgotten. Take advantage of the rainy weekend, a general record of today's notes, or make up for some of the C # knowledge of some blind spots. Compile/Execute Process: C # History, with the help of who, nonsense all skip, look at the picture:

Note: In order to save time, this figure is not a book map;

noun annotations: clr: The Common Language runtime (Common Language Runtime), is a "runtime" used by multiple languages, only runs (interprets) managed modules (IL)//. NET under managed DLLs, EXE files need to rely on the CLR to interpret the run; C # virtual machine interpreted language) IL: Intermediate language (intermediate Language); The code generated when the compiler compiles the source code. At run time, the CLR edits it to the cost machine CPU instruction;//C #, VB and other compilers, compiled files (assemblies) IL, also known as "managed modules" (containing intermediate languages and metadata) managed module components: Managed header identification (PE32, pe32+) understood as x32, X6　　4; CLR header, contains some identifying information such as the required CLR version, metadata: Describes the classes and members defined in the source code, as well as the class and members referenced by the code, or the IntelliSense hint of the Visual Studio IDE. JIT:CLR compiler, responsible for compiling IL machine code (CPU instructions),//Jitcompiler The native code is optimized and then dropped to the CPU execution;//C # compiler has been optimized very well, a development language is mostly depends on their compiler to do good or bad. //interested in using IL_DASM anti-compilation to see, you can also look at some foreign companies specifically to do the compiler, this article does not explain the compilation process;

On C # CLR execution module