《CLR Via C#》第三版：深入解析C#

4星 · 超过85%的资源需积分: 0 51 浏览量更新于2024-07-22 收藏 11.89MB PDF 举报

"CLR via Csharp3rdEdition《CLR Via C#》第三版+加目录" 《CLR Via C#》是Jeffrey Richter撰写的一本深入解析.NET Framework Common Language Runtime (CLR) 的经典书籍，主要面向C#程序员。这本书详细介绍了如何通过C#语言来理解和利用.NET Framework的底层机制，对于想要深入理解.NET平台的开发者来说，是一本不可或缺的参考书。书中涵盖了以下关键知识点： 1. CLR基础：讲解了CLR的作用和工作原理，包括类型系统、内存管理（如垃圾回收）、异常处理、线程管理和代码执行模型等。 2. C#语言特性：深入剖析C#语言的各个版本的新特性，比如匿名方法、LINQ、Lambda表达式、委托和事件、泛型、属性、接口、枚举、结构等。 3. .NET框架类库：探讨了.NET Framework提供的大量类库，如System.Collections、System.IO、System.Threading等命名空间中的核心类，以及如何利用这些类进行高效的编程。 4. 应用程序域和安全性：解释了应用程序域的概念，它是.NET中的隔离和安全策略的基础，同时讲解了代码访问安全性和权限管理。 5. 虚拟执行系统：详细阐述了JIT编译器的工作流程，包括动态编译、优化以及如何影响性能。 6. 高级话题：涵盖元数据、反射、IL（Intermediate Language）以及如何使用ILDASM和Reflector工具查看和分析.NET程序。 7. 扩展性与自定义：讨论了如何使用托管扩展、宿主控制接口（Host Control Interface, HCI）自定义CLR的行为，以及如何编写COM互操作组件。 8. 性能优化：提供了一些最佳实践和技巧，帮助开发者编写出高效、优化的.NET代码。 9. 并发和多线程：深入分析.NET中的多线程编程，包括同步、异步操作、线程池以及并发容器。 10. 部署和调试：介绍.NET应用程序的部署策略，以及使用Visual Studio和其他工具进行调试的方法。这本书的英文版还包含了作者自己添加的目录，方便读者快速定位所需内容。虽然书中的内容是英文的，但对有志于深入学习.NET开发的程序员来说，克服语言障碍将是一次宝贵的学习机会。书中丰富的示例和深入的讲解，将帮助读者从底层理解.NET Framework，提升编程技能。

xvi

Introduction

Web Forms, and so on, the technologies presented in the book are applicable to all these

application types.

The book addresses Microsoft Visual Studio 2010, .NET Framework version 4.0, and version 4.0

of the C# programming language. Since Microsoft tries to maintain a large degree of back-

ward compatibility when releasing a new version of these technologies, many of the things

I discuss in this book apply to earlier versions as well. All the code samples use the C#

programming language as a way to demonstrate the behavior of the various facilities. But,

since the CLR is usable by many programming languages, the book’s content is still quite

applicable for the non-C# programmer.

Note

You can download the code shown in the book from Wintellect’s Web site

(http://Wintellect.com). In some parts of the book, I describe classes in my own Power

Threading Library. This library is available free of charge and can also be downloaded from

Wintellect’s Web site.

Today, Microsoft offers several versions of the CLR. There is the desktop/server version, which

runs on 32-bit x86 versions of Microsoft Windows as well as 64-bit x64 and IA64 versions

of Windows. There is the Silverlight version, which is produced from the same source code

base as the desktop/server version of the .NET Framework’s CLR. Therefore, everything in this

book applies to building Silverlight applications, with the exception of some differences in

how Silverlight loads assemblies. There is also a “lite” version of the .NET Framework called

the .NET Compact Framework, which is available for Windows Mobile phones and other

devices running the Windows CE operating system. Much of the information presented in

this book is applicable to developing applications for the .NET Compact Framework, but this

platform is not the primary focus of this book.

On December 13, 2001, ECMA International (http://www.ecma-international.org/) accepted

the C# programming language, portions of the CLR, and portions of the FCL as standards.

The standards documents that resulted from this have allowed other organizations to build

ECMA-compliant versions of these technologies for other CPU architectures, as well as other

operating systems. In fact, Novell produces Moonlight (http://www.mono-project.com

/Moonlight), an open-source implementation of Silverlight (http://Silverlight.net) that is

primarily for Linux and other UNIX/X11-based operating systems. Moonlight is based on the

ECMA specications. Much of the content in this book is about these standards; therefore,

many will nd this book useful for working with any runtime/library implementation that ad-

heres to the ECMA standard.

Introduction

xvii

Note

My editors and I have worked hard to bring you the most accurate, up-to-date, in-depth,

easy-to-read, painless-to-understand, bug-free information. Even with this fantastic team

assembled, however, things inevitably slip through the cracks. If you nd any mistakes in this

book (especially bugs) or have some constructive feedback, I would greatly appreciate it if you

would contact me at JeffreyR@Wintellect.com.

Dedication

To KristinWords cannot express how I feel about our life together. I cherish our family and

all our adventures. I’m lled each day with love for you.

To Aidan (age 6) and Grant (age 2)You both have been an inspiration to me and have

taught me to play and have fun. Watching the two of you grow up has been so rewarding

and enjoyable for me. I am lucky to be able to partake in your lives. I love and appreciate you

more than you could ever know.

Acknowledgments

I couldn’t have written this book without the help and technical assistance of many people.

In particular, I’d like to thank my family. The amount of time and effort that goes into writing

a book is hard to measure. All I know is that I could not have produced this book without the

support of my wife, Kristin, and my two sons, Aidan and Grant. There were many times when

we wanted to spend time together but were unable to due to book obligations. Now that the

book project is completed, I really look forward to adventures we will all share together.

For this book revision, I truly had some fantastic people helping me. Christophe Nasarre,

who I’ve worked with on several book projects, has done just a phenomenal job of verifying

my work and making sure that I’d said everything the best way it could possibly be said. He

has truly had a signicant impact on the quality of this book. As always, the Microsoft Press

editorial team is a pleasure to work with. I’d like to extend a special thank you to Ben Ryan,

Valerie Woolley, and Devon Musgrave. Also, thanks to Jean Findley and Sue McClung for

their editing and production support.

Support for This Book

Every effort has been made to ensure the accuracy of this book. As corrections or changes

are collected, they will be added to a Microsoft Knowledge Base article accessible via the

Microsoft Help and Support site. Microsoft Press provides support for books, including

instructions for nding Knowledge Base articles, at the following Web site:

http://www.microsoft.com/learning/support/books/

Chapter 1

The CLR’s Execution Model

In this chapter:

Compiling Source Code into Managed Modules............................1

Combining Managed Modules into Assemblies............................5

Loading the Common Language Runtime.................................6

Executing Your Assembly’s Code.........................................9

The Native Code Generator Tool: NGen.exe...............................18

The Framework Class Library............................................20

The Common Type System.............................................22

The Common Language Specication....................................25

Interoperability with Unmanaged Code..................................29

The Microsoft .NET Framework introduces many new concepts, technologies, and terms. My

goal in this chapter is to give you an overview of how the .NET Framework is designed, intro-

duce you to some of the new technologies the framework includes, and dene many of the

terms you’ll be seeing when you start using it. I’ll also take you through the process of build-

ing your source code into an application or a set of redistributable components (les) that

contain types (classes, structures, etc.) and then explain how your application will execute.

Compiling Source Code into Managed Modules

OK, so you’ve decided to use the .NET Framework as your development platform. Great! Your

rst step is to determine what type of application or component you intend to build. Let’s

just assume that you’ve completed this minor detail; everything is designed, the specica-

tions are written, and you’re ready to start development.

Now you must decide which programming language to use. This task is usually difcult

because different languages offer different capabilities. For example, in unmanaged C/C++,

you have pretty low-level control of the system. You can manage memory exactly the way

you want to, create threads easily if you need to, and so on. Microsoft Visual Basic 6, on the

other hand, allows you to build UI applications very rapidly and makes it easy for you to

control COM objects and databases.

The common language runtime (CLR) is just what its name says it is: a runtime that is usable by

different and varied programming languages. The core features of the CLR (such as memory

Part ICLR Basics

management, assembly loading, security, exception handling, and thread synchronization)

are available to any and all programming languages that target it—period. For example, the

runtime uses exceptions to report errors, so all languages that target the runtime also get

errors reported via exceptions. Another example is that the runtime also allows you to create

a thread, so any language that targets the runtime can create a thread.

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 mathemati-

cal or nancial 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.

Microsoft has created several language compilers that target the runtime: C++/CLI, C# (pro-

nounced “C sharp”), Visual Basic, F# (pronounced “F sharp”), Iron Python, Iron Ruby, and an

Intermediate Language (IL) Assembler. In addition to Microsoft, several other companies, col-

leges, and universities have created compilers that produce code to target the CLR. I’m aware

of compilers for Ada, APL, Caml, COBOL, Eiffel, Forth, Fortran, Haskell, Lexico, LISP, LOGO,

Lua, Mercury, ML, Mondrian, Oberon, Pascal, Perl, Php, Prolog, RPG, Scheme, Smalltalk, and

Tcl/Tk.

Figure 1-1 shows the process of compiling source code les. As the gure shows, you can cre-

ate source code les written in any programming language that supports the CLR. Then you

use the corresponding compiler to check the syntax and analyze the source code. Regardless

of which compiler you use, the result is a managed module. A managed module is a standard

32-bit Microsoft Windows portable executable (PE32) le or a standard 64-bit Windows

portable executable (PE32+) le that requires the CLR to execute. By the way, managed

assemblies always take advantage of Data Execution Prevention (DEP) and Address Space

Layout Randomization (ASLR) in Windows; these two features improve the security of your

whole system.

剩余895页未读，继续阅读

sinat_23286851

粉丝: 0
资源: 1

《CLR Via C#》第三版：深入解析C#

CLR via C# (Third Edition, 高清非扫描带书签)

Introduction-to-algorithm-3rdEdition 算法导论（英文第3版）

【水果识别】基于matlab GUI形态学水果大小识别【含Matlab源码 920期】.md

【瑕疵检测】基于matlab瓶盖瑕疵检测【含Matlab源码 730期】.md

Shapely-1.6.4.post2-cp35-cp35m-win_amd64.whl

Apache Flink CEP复杂事件处理详解及实战案例

SSM+JSP在线网课管理系统答辩PPT.pptx

稳压罐sw16_三维3D设计图纸.zip

英语知识应用网站 JAVA毕业设计 源码+数据库+论文 Vue.js+SpringBoot+MySQL.zip

大模型部署-基于TensorRT-LLM部署Qwen1.5大语言模型-附项目源码+流程教程-优质项目实战.zip

最新资源

英语知识应用网站 JAVA毕业设计源码+数据库+论文 Vue.js+SpringBoot+MySQL.zip