Comment on "Applied Microsoft .NET Framework Programming"
I also read a masterpiece "Applied Microsoft .NET Framework Programming". This is my second reading this book. The first reading is an e-book. At that time, I was deeply admired to Richter. Speaking of classic books under Win32, absolutely refer to Richter's Programming Applications for Microsoft Windows. I have already heard it earlier, but I have never passed the case. But in this book, I really feel the style of the master. Many of them are not only an elaboration of the principle of .NET Framework, and many of these qualities have been personalized. At this point, Richter is very good at "principle" and "practical" scale, and many of the code have direct help to I can say. Moreover, Richter's evaluation is really a master's evaluation, and it is also to take okward for .NET Framework's bug.
At that time, I was more in Richter I yearn (the first two is the commander Karl Richter and the pianist sviatoslav richter).
It may be the reason for the personal level, and the content of this book seems to be a bit "non-entry". I feel that there is no certain programming experience, it is easy to see this book. In particular, some chapters near the head.
Recently I have never read this book, and I hope is a paper version. At the time, I went shopping at the bookstore, I didn't find the photocopy version, so I bought a Chinese version published by Mr. Li Jianzhong, Tsinghua University Publishing House. Suddenly, this is a rare hope to see, and it will recommend it to others to say that the translation works, the translation of Mr. Li Jianzhong and its rigorous, and the "translation" in the relevant part also makes people have to recognize it. The component, he also pointed out part of the part of Richter. Language is easy to understand, and correct me forgetful and misunderstanding. And I like to write "Into the painting" in the book "annotation" is back. After reading it, it's too much. :)
Introduction is a simple introduction to .NET Framework, the INTROT FRAMEWORK has proposed the purpose, idea, and the basis of the .NET Framework that appears .NET Framework.
Part i: Basics of the Microsoft .NET Although the "Basics" is written on the big headline, it should be the most difficult part of this book, but it is also understanding that .NET Framework is very important. CLR, JITComplie, IL, GAC concept and implementation; module (Module), assembly, content, and way of use. These can be described as essential in .NET Framework, it is necessary to understand these. But also, as in the book Richter said: "For the most part, you do not need to know about or understand how the CLR gets loaded For most programmers, this special information allows the application to just run, and there nothing's. "if you're not intended in this subject, Feel free to skip to the next section.", if you only need to use .NET Framework, More important is the back of the back. Part II: Working with Types and The Common Language Runtime This is a very important part of the .NET Framework, whether anyone can't let go, must understand. Personally, the conceptual content is relatively simple, but it is more important, especially the boxing part. Moreover, there is a very useful part of the instance code for equals operation, that is, explains the way Equals operations and the reason, but also can be used directly. In fact, this is also a feature of this book. This book is indeed necessary to become the case necessary for .NET Framework programmers.
Part III: Designing Types This part can be said ... In the next book, people who have a certain .NET Framework code experience can easily understand, but the code in "incident" is able to use directly. really not bad.
Part IV: Essential Types has two very important parts. It is especially in Chapter 12, "Working with Text" is also (in fact, see the space of this chapter knows). The mastery of this chapter will largely affect the quality and efficiency of code written, where the elaboration of System.String and StringBuilder can be said to be quite exciting. For "delegate", I think I can combine with Chapter 11, "Events", after all, "Events" is a direct and typical way of use of "commission". The content of this part is important, but it is not difficult to understand it.
Part V: Managing Types Chapter 18 Write the concept, mechanism, and the comparison of the comparison of the traditional error operation below Win32 below, but Richter's recommendations made to customize the exception can be described as important. The interpretation of the garbage collection mechanism in Chapter 19 is very thorough, although it is not all people need to understand, but after understanding some of the masters of the CLR can be able to rely on reasonable use of garbage collection mechanisms to increase the efficiency of the code . Similarly, it is mentioned that small optimization skills. The last chapter, I think it is one of the essence of .NET Framework, this whole book seems to have "first echo". This chapter combines CLS Host to reveal the content of Appdomain, and also the focus of powerful reflex mechanism in .NET. The sample code is also a reference value. The whole book is probably described, personal thinking, Part II to Part IV is suitable for everyone to read, and must read, as for Part i and chapter 20, readers choose to read it according to their own requirements, if not It doesn't matter, more practical, maybe, "suddenly open".
This book is indeed .NET Framework developer's case must have a feeling of meeting it. However, this book seems to be just a soft in terms of P / Invoke and COM interoperability. If the reader is interested in this, it may be necessary to find information. Compared with Essential .NET, this book has reduced a certain theoretical height, which has added a lot of practical components. But even so, I still don't think it is suitable for entry, huh, huh :)
Replenishment (revision): Suddenly, I also want to re-read the Essential .NET of Don Box, and I have intended to see the Chinese version. Because the Chinese version of the cover is beautiful, huh, huh. The legendary Essential COM and Essential XML have not met. The first contact is still .NET Framework.
