CLR通过C#探索Windows/.NET编程

需积分: 14 98 浏览量更新于2024-07-25 收藏 36.21MB PDF 举报

"CLR via C#" 是一本由著名技术作家 Jeffrey Richter 撰写的关于 .NET Framework 中 Common Language Runtime (CLR) 和 C# 编程的深入指南。这本书由 Microsoft Press 出版，作者以其在 Windows 和 .NET 领域的专业知识，为读者提供了丰富的编程实践经验。这本书主要探讨了以下几个方面的知识点： 1. **Common Language Runtime (CLR)**：CLR 是 .NET Framework 的核心组件，负责执行托管代码、垃圾收集、类型安全、异常处理以及线程管理。书中会详细解释 CLR 如何提供跨语言互操作性，以及如何通过它来实现高效、安全的代码执行环境。 2. **C# 语言深度解析**：作为 .NET 平台上主要的编程语言，C# 在这本书中得到了详尽的阐述。内容可能包括语法特性、面向对象编程、泛型、LINQ（Language Integrated Query）、异步编程、元数据和反射等高级主题。 3. **.NET Framework 类库**：书中可能会涵盖 .NET Framework 提供的各种类库，如 System.Collections、System.IO、System.Net 和 System.Xml，这些类库提供了丰富的功能，用于文件操作、网络通信和数据处理等。 4. **内存管理和垃圾回收**：Richter 将深入讨论 CLR 的内存管理机制，包括如何分配和释放内存，以及垃圾回收的工作原理，帮助开发者理解和优化应用程序的性能。 5. **类型系统与元数据**：.NET 中的类型系统是其强类型语言的基础，元数据则为类型提供了描述信息。书中可能涉及类型继承、接口实现、属性和事件，以及元数据在程序集之间的交互作用。 6. **安全性与权限模型**：.NET Framework 提供了一套强大的安全性模型，包括代码访问安全性和角色基础的安全性。书中的这部分内容将帮助开发者构建安全的应用程序，并理解如何控制代码的执行权限。 7. **调试与诊断工具**：Richter 可能会介绍如何使用 Visual Studio 和其他工具进行 .NET 应用程序的调试和性能分析，这对于优化和解决问题至关重要。 8. **并发与并行计算**：随着多核处理器的普及，了解如何编写并发和并行代码变得越来越重要。书中会涵盖线程、任务、同步原语和并发集合等概念，以及如何利用 .NET 提供的并发工具。 9. **Windows 应用程序开发**：虽然主要集中在 .NET 上，但鉴于 Richter 对 Windows 开发的深厚背景，书中的某些章节可能也会讨论如何使用 CLR 和 C# 开发桌面应用程序，包括窗口消息、服务和资源管理等。 10. **.NET Framework 的最新发展**：考虑到出版年份，书中可能还会包含 .NET Framework 当时的最新特性和更新，如 Silverlight 或 Windows Phone 开发的相关内容。 “CLR via C#”是一本全面且深入的教程，适合有经验的 .NET 开发者深入学习平台内部机制，以及对 .NET 新手提供了一个全面的指导。通过阅读这本书，读者可以提升对 .NET Framework 和 C# 编程的理解，从而编写出更高效、更健壮的代码。

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

JimmyTsai

粉丝: 0
资源: 1

CLR通过C#探索Windows/.NET编程

CLR via C# 第四版.pdf

CLR via C# 第4版.pdf

.NET CLR via C#(第4版) 最新完整版 高清文字版

CLR via c#

CLR Via C#

clr via c#

CLR via C# 3rd

CLR via C#PDF

CLR via C# 电子书

CLR via C#.pdf

最新资源

.NET CLR via C#(第4版) 最新完整版高清文字版