深入理解CLR与.NET Framework 4.0：C#实战指南

5星 · 超过95%的资源需积分: 10 125 浏览量更新于2023-06-25 收藏 36.21MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

《CLR via C# 第三版》是一本由Jeffrey Richter所著的专业书籍，专门针对Microsoft .NET Framework 4.0及其底层组件Common Language Runtime (CLR)进行了深度剖析。该书分为五个部分，共29章，旨在帮助读者理解和掌握如何在C#编程环境中有效地设计、开发和调试基于.NET的应用程序。第一部分，"CLR基础"，为读者提供了对.NET框架运行时的核心概念的入门讲解，包括.NET架构、垃圾回收机制、JIT编译器以及类型系统的基础。这部分内容对于理解后续章节的高级主题至关重要，因为它为构建高效和安全的.NET应用奠定了基础。第二部分，"设计类型"，深入探讨了如何利用CLR的特性来设计和实现可扩展性、模块化和面向对象的程序。这部分内容涵盖了接口、抽象类、泛型、命名空间和元数据等关键设计元素，有助于读者创建高质量的代码结构。第三部分，"基本类型"，详细介绍了.NET框架中的各种基本数据类型，如值类型（如整数、浮点数、布尔值）和引用类型（如类和对象）。这部分内容是所有C#开发者必须掌握的基础，以便正确地组织和操作数据。第四部分，"实用特性"，则着重于展示CLR和.NET框架的高级特性和工具，如并发编程、异步编程模型、内存管理优化、动态类型以及C#语言的一些高级特性。这部分内容对于追求效率和性能优化的开发者尤其有用。第五部分，"线程处理"，是全书的亮点，作者将花费大量篇幅深入讲解线程安全、多线程编程、任务并行库（TPL）以及.NET Framework提供的线程管理工具。这部分内容对于任何涉及多线程编程的开发者来说都是必不可少的，因为线程并发是现代应用程序性能的关键要素。此外，书中还包含了版权信息、版权声明、国际版本购买渠道以及微软的一些技术产品如Active Directory、DirectX、SQL Server等的简介，这些都是了解.NET生态系统的重要背景知识。通过阅读这本书，读者不仅能提升C#编程技能，还能深入了解CLR的工作原理，从而成为更加全面的.NET开发者。

资源详情

资源推荐

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页未读，继续阅读

test222222

粉丝: 0
资源: 1

会员权益专享

深入理解CLR与.NET Framework 4.0：C#实战指南

clr via c# 第三版

CLR via C#第三版

CLR via C# 第三版 pdf英文版

clr via c# 中文版

clr via c#下载

clr via c#(第4版) 完整源代码

clr via c# pdf 下载

NET CLR via C#

clr via c#

clr.via.c# 第4版 文字版

clr via第4版中文pdf

C++/CLR 使用C# task

c#方向比较著名的文献

C++/CLR 使用C# task 且处理带界面的代码

clr 封装dll给c#调用

C# clr dll

C# 获取clr的字典

sqlserver 调用c# CLR 发送http请求

c# CLR 发送http请求

.net相关电子书推荐

会员权益专享

最新资源

clr.via.c# 第4版文字版