目录 Foreward Introduction Part Ⅰ CLR Basics 1 The CLRs Execution Model Compiling Source Code into Managed Modules Combining Managed Modules into Assemblies Loading the Common Language Runtime Executing Your Assemblys Code IL and Verification Unsafe Code The Native Code Generator Tool: NGen.exe The Framework Class Library The Common Type System The Common Language Specification Interoperability with Unmanaged Code 2 Building, Packaging, Deploying, and Administering Applications and Types 3 Shared Assemblies and Strongly Named Assemblies Part Ⅱ Designing Types 4 Type Fundamentals 5 Primitive, Reference, and Value Types 6 Type and Member Basics 7 Constants and Fields 8 Methods 9 Parameters 10 Properties 11 Events 12 Generics 13 Interfaces Part Ⅲ Essential Types 14 Chars, Strings, and Working with Text 15 Enumerated Types and Bit Flags 16 Arrays 17 Delegates 18 Custom Attributes 19 Nullable Value Types Part Ⅳ Core Facilities 20 Exceptions and State Management 21 Automatic Memory Management (Garbage Collection) 22 CLR Hosting and AppDomains 23 Assembly Loading and Reflection 24 Runtime Serialization Part Ⅴ Threading 25 Thread Basics 26 Compute-Bound Asynchronous Operations 27 I/O-Bound Asynchronous Operations 28 Primitive Thread Synchronization Constructs 29 Hybrid Thread Synchronization Constructs Index
精彩内容 In fact, at runtime, the CLR has no idea which programming language the developer used for the source code. This means that you should choose whatever programming language allows you to express your intentions most easily. You can develop your code in any programming language you desire as long as the compiler you use to compile your code targets the CLR. So, if what I say is true, what is the advantage of using one programming language over another? Well, I think of compilers as syntax checkers and “correct code” analyzers. They examine your source code, ensure that whatever you've written makes some sense, and then output code that describes your intention. Different programming languages allow you to develop using different syntax. Don't underestimate the value of this choice. For mathematical or financial applications, expressing your intentions by using APL syntax can save many days of development time when compared to expressing the same intention by using Perl syntax, for example.
以下为对购买帮助不大的评价