Jeffrey Richter的CLR Via C# 第三版：经典.net开发指南

需积分: 10 201 浏览量更新于2024-07-24 收藏 45.53MB PDF 举报

《CLR Via C# 第三版》是由Jeffrey Richter所著的一本备受.NET程序员推崇的经典之作。这本书由微软出版社出版，隶属于微软公司，位于美国华盛顿州雷德蒙德市。版权由Jeffrey Richter所有，未经书面许可，书中内容不得任何形式的复制或传输。本书专注于.NET框架中的Common Language Runtime (CLR)技术，这是.NET平台的核心组件，负责执行.NET应用程序的字节码。CLR提供了类型系统、垃圾回收、线程管理以及异常处理等功能，是理解和掌握.NET编程的关键。作者Jeffrey Richter以其深入浅出的风格，通过C#语言作为主要讲解工具，帮助读者深入了解CLR的工作原理、优化策略以及与.NET框架其他组件如.NET Framework Class Library (FCL)的集成。在《CLR Via C# 第三版》中，你将学习到的内容包括但不限于： 1. **CLR概述**：介绍CLR的设计理念、架构以及其在.NET框架中的角色，以及它如何支持跨语言、跨平台的开发。 2. **类型系统和内存管理**：探讨.NET的元数据、托管类型、垃圾回收机制以及如何编写高效且内存安全的代码。 3. **执行引擎**：剖析.NET编译器如何将C#源代码编译成中间语言（IL），以及CLR如何解释并执行这些IL指令。 4. **安全管理**：了解Authenticode签名、安全沙箱和.NET的安全模型，确保应用程序的安全运行。 5. **并发和线程**：介绍.NET的线程池、异步编程以及任务并行库（TPL）在多线程环境下的应用。 6. **异常处理**：深入理解.NET的异常处理模型，以及如何设计健壮的错误处理机制。 7. **性能优化**：提供实用的性能调优技巧，包括JIT编译、内存分配和缓存策略等。 8. **与其他技术的交互**：例如与Windows API、数据库（如SQL Server）、Web服务（如XML Web Services）以及用户界面（如Windows Forms、WPF）的集成。《CLR Via C# 第三版》是一本极具价值的参考书，无论你是初入.NET世界的开发者，还是希望深化对CLR理解的专业人员，都将从中获益匪浅。同时，由于Microsoft Press国际版的联系方式也被提及，读者可以寻求全球范围内的更多资源和支持。

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 Kristin Words 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

2 Part I CLR 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页未读，继续阅读

shenhaili1219

粉丝: 0
资源: 1

Jeffrey Richter的CLR Via C# 第三版：经典.net开发指南

clr via c# 第三版

CLR via C# 第三版

CLR via C#第三版

CLR VIA C# 第三版 英文版

CLR via C# 第三版 pdf英文版

CLR via C# 第三版.pdf

CLR via C# 第三版 中文版 第二部分

CLR via C#第三版(英文版)

CLR via C#第三版（二）

clr via c# 第三版 中文 part1

最新资源

CLR VIA C# 第三版英文版

CLR via C# 第三版中文版第二部分

clr via c# 第三版中文 part1