Part 1 of CLR. via. C # Third Edition (1 ),

Part 1 of CLR. via. C # Third Edition (1 ),

Recently, I began to carefully read the book CLR. via. C #3. Reading pdf documents is really tiring. It is recommended that you buy books for eligible friends.

My notes are used to record my understanding of this book, simplify the logic, and summarize what I think is the main point. The basic things will not be elaborated too much.

The first part is about the basis of CLR.

First, let's repeat the concept of CLR: "CLR is a" RunTime "that can be used by multiple programming languages ". You can use any programming language to develop code, as long as the compiler is oriented to CLR ". Here we need to re-explain the sentence "as long as the compiler is CLR oriented. Beginners generally do not agree that the. net platform is a cross-language, or the so-called "cross-language" is a language launched by Microsoft. This is actually wrong. Any language can create its own compiler for CLR. The well-known Iron Ruby, Perl, and PHP all have CLR-oriented compilers. Figure 1-1 shows the process of compiling source code files.

It is important to know that CLR does not actually work with the hosting module, but works with the Assembly. The Assembly contains other files such as the managed module and resource file.

IL (intermediate language) can be written in assembly language. The JIT (just in time) in CLR is also called the Real-time compiler. There is a JITComplier () function in it. This function is responsible for converting the IL of the method to be executed to the local CPU command.

Class:

When a method is executed, it is called twice. (The tentative method is Test ())

First call:

JITCompiler () will compile the IL code of the Test () method to the local CPU command (this command will be saved to a dynamically allocated memory block ).), The Test () method is executed through JITComplier in the memory block (including the IL of the method to be searched, the IL of the verification method, compilation, and execution ).

Second call:

Skip JITCompiler () completely, and the Test () method is executed again in the memory.

The two execution steps 1-4, 1-5 are shown below:

Note that the local CPU command is stored in the dynamic memory. Once the program is terminated, the local CPU command will be discarded.

The difference between the Debug version and the Release version is, in essence, whether the IL code quality and the JIT local code quality have been optimized. In terms of performance, it is best to use the Release version for program deployment and Release.

This part includes program packaging, deployment, assembly information, and so on. I will not discuss it here.

What about clr via c?

For the first time, I felt very difficult, but it was not very difficult to read my head. I can learn more from this book. If I use Keni, this is an entry-level book, because after reading it, you will have a lot of questions with these ......

CLR via C # Can I copy a third-edition ebook? Email: 10139713 @ qqcom

This is the book. You need it.

CLRviaC # Author: (US) Number of pages: 778 published on: 2010.09 Introduction: This book targets CLR and. NET Framework 4.0 is deeply and comprehensively discussed. It also introduces how to use them for design, development, and debugging. Chapter 29, Part 5. Part I introduces CLR basics, Part II explains how to design types, Part III...