C#编程思想深度解析：经典指南与实践

需积分: 0 180 浏览量更新于2024-07-21 收藏 4.5MB PDF 举报

《思考在C#》(Thinking in C#)是由Larry O'Brien和Bruce Eckel合著的经典教材，由Prentice Hall出版，出版地为美国新泽西州上萨德尔里弗。这本书旨在为读者提供全面的C#编程理解，无论是对于初学者还是已经熟悉其他编程语言的开发者，都是一本极具价值的学习工具。全书分为18章，涵盖了C#语言的基础和进阶主题。第1章介绍计算机语言的基本概念，帮助读者明确学习目标，为接下来的内容打下基础。第2章到第18章分别深入探讨了： 1. **那些能者，代码编写** - 引导读者理解编程的概念，强调实践的重要性。 2. **对象入门** - 介绍面向对象编程（Object-Oriented Programming, OOP）的基本原则和C#中的类与对象。 3. **Hello, Objects** - 实例化对象和方法的使用，展示了C#的基本语法和操作。 4. **控制程序流程** - 学习条件语句、循环、函数和递归等控制结构。 5. **初始化与清理** - 阐述变量声明、初始化以及垃圾回收的重要性。 6. **隐藏实现** - 探索封装和访问修饰符，如何保护类的内部细节。 7. **类的重用** - 学习继承、接口和抽象类，促进代码复用。 8. **接口与实现** - 探讨接口的定义和如何实现多态性。 9. **耦合与内聚** - 讨论软件设计原则，优化代码质量。 10. **收集对象** - 理解内存管理，包括对象生命周期和引用计数。 11. **异常处理** - 学习如何捕获和处理运行时错误，提升程序健壮性。 12. **I/O操作** - 描述C#中的输入/输出操作，包括文件系统和网络通信。 13. **反射与属性** - 展示元数据和自省能力的应用。 14. **Windows Forms编程** - 学习GUI编程，创建用户界面。 15. **GDI+概述** - 图形设备接口(GDI+)在图形处理方面的应用。 16. **多线程编程** - 如何在C#中设计并发和并行应用。 17. **XML** - 掌握C#中的XML处理，包括DOM和XPath。 18. **Web编程** - 了解C#在Web开发中的角色，如ASP.NET。附录部分A针对Visual Basic程序员，B则为Java程序员提供了从C#视角的对比，让不同背景的开发者能够更好地迁移知识。C章节介绍了使用NUnit进行测试驱动开发，D章节涉及移动开发，如在Pocket PC上的编程。E部分列出了C#编程指南，为实践中的最佳实践提供建议。最后，附录包含词典、类、方法和属性的交叉参考，以及索引，帮助读者查找特定主题。通过阅读《思考在C#》，读者不仅能掌握C#语言，还能深入理解面向对象编程的核心概念，提升软件开发技能，并学会如何高效地利用C#进行各种应用场景的开发。

ii Thinking in C# www.ThinkingIn.NET

library classes and methods in the area. Hopefully, some topics will excite your

interest and you will seek out a deeper understanding of the underlying

principles.

Every chapter in this book is worthy of book-length discussion and Thinking in

C# necessarily glosses over many issues. Rather than hide these decisions in

academic rhetoric, this book tries to make explicit the subjective opinions of the

authors, Larry O’Brien and Bruce Eckel. Additionally, neither of us is in the

employ of Microsoft

and both of us are fairly jaded when it comes to languages,

frameworks, and implementations. We do not hesitate to criticize design

decisions with which we disagree nor do we pause when it comes to crediting

Java as an important influence as both a marketing and technical influence on C#

and .NET. Both of us have been programming since the 1970s and writing and

teaching on these subjects since the ’80s, so our opinions may be judged

incorrect, but we come to those opinions by experience.

Prerequisites

This book assumes that you have some programming familiarity: you understand

that a program is a collection of statements, the idea of a

subroutine/function/macro, control statements such as “if” and looping

constructs such as “while,” etc. However, you might have learned this in many

places, such as programming with Microsoft Office’s Visual Basic for Applications

or working with a tool like Perl. As long as you’ve programmed to the point where

you feel comfortable with the basic ideas of programming, you’ll be able to work

through this book.

The book will be easiest for Visual Basic, Delphi, or Java programmers. Visual

Basic programmers will be familiar with many library names and several of the

programming models, Delphi programmers will recognize in C# the influence of

Anders Hejlsberg, and Java programmers will find the hardest thing about

moving to C# is getting used to a different naming convention. If you don’t have a

background in those languages, don’t count yourself out, although naturally it

means that you will be required to expend a little more effort.

This book does not assume that you’re familiar with object-oriented

programming (OOP) and the first half of the book can be seen as an extended

tutorial on object-oriented programming at least as much as a tutorial on C# per

se. No formal background in computer science is expected.

Larry has been paid to write technical white papers for Microsoft.

Preface: Computer Language iii

Although references will often be made to language features in other languages

such as C++ and Java, these are not intended to be insider comments, but instead

to help all programmers put C# in perspective with those languages. All good

programmers are polyglots and the greatest value proposition of the .NET

Framework is that it supports multiple languages.

Learning C#

Picasso is reputed to have said “Computers are worthless; they can only give you

answers.” The same could be said of books. No book can teach you C#

programming, because programming is a creative process. The only way to learn

any language is to use it in a variety of situations, to gradually internalize it as you

solve increasingly difficult problems with it. To learn C#, you must start

programming in C#.

This is not to say that the best way to learn C# is on the job. For one thing,

companies don’t typically allow programmers to work in a language in which they

have no experience. More significantly, your job is to deliver value to your

customers, not to learn the nuances of C# and the .NET Framework.

For many people, seminars are the best environment for rapid learning. There

are many reasons for this: the interactions with the teachers and fellow students,

the explicit dedication of several days to achieving specific educational goals, or

just being out of the office and away from email and meetings. One of the authors

(Bruce) has been teaching object-oriented programming in multiday seminars

since 1989. The structure of this book is highly influenced by those experiences.

As the chair of the C++ and Java tracks at the Software Development conference,

Bruce discovered that speakers tended to give the typical audience too many

topics at once. Sometimes this was because they were striving to present an

example that was “realistic” and therefore unfocused. Other times it stemmed

from a fear of underserving the more experienced in the audience. Over the years,

Bruce developed many presentations, iteratively developing a scope and sequence

for teaching object-oriented programming in a language-specific manner. This

curriculum has been the core of many products: books, CD-ROMs, and seminars

for a variety of languages including C++, Java, and, now, C#.

There are three notable characteristics of this curriculum:

♦ It has a broad scope, from fundamental topics such as “how does one

compile a program?” to professional challenges such as thread-safe

design

iv Thinking in C# www.MindView.net

♦ It is outcome-oriented: the goal is to give the learner the basic skills for

professional object-oriented development in the language

♦ It is dependent on the learner’s active engagement with the samples and

exercises

Although this book is influenced by the seminars and books that preceded it, it is

not just seminar notes. More than anything, the book is designed to serve the

solitary reader who is struggling with a new programming language.

Goals

Like its immediate predecessor Thinking in Java, this book is structured around

the process of teaching the language. In particular, the structure is based on the

way the language can be taught in seminars. Chapters in the book correspond to

what experience has taught is a good lesson during a seminar. The goal is to get

bite-sized pieces that can be taught in a reasonable amount of time, followed by

exercises that are feasible to accomplish in a classroom situation.

The goals of this book are to:

1. Present the material one simple step at a time so that you can easily

digest each concept before moving on.

2. Use examples that are as simple and short as possible. This generally

prevents “real world” problems, but it’s better to understand every detail

of an example rather than being impressed by the scope of the problem it

solves.

3. Carefully sequence the presentation of features so that you aren’t seeing

something that you haven’t been exposed to. Of course, this isn’t always

possible; in those situations, a brief introductory description is given.

4. Give a pragmatic understanding of the topic, rather than a

comprehensive reference. There is an information importance hierarchy,

and there are some facts that 95 percent of programmers will never need

to know and that just confuse people and add to their perception of the

complexity of the language. To take an example from C#, if you

memorize the operator precedence table on page 118, you can write

clever code. But if you need to think about it, it will also confuse the

reader/maintainer of that code. So forget about precedence, and use

parentheses when things aren’t clear.

5. Keep each section focused enough so that the range of topics covered is

digestible. Not only does this keep the audience’s minds more active and

剩余956页未读，继续阅读

wordchao

粉丝: 0
资源: 2

C#编程思想深度解析：经典指南与实践

Thinking in C#

thinking in linq中文

thinking in patterns 百度百科

thinking in uml pdf 电子书

thinking in c++ 中文版 pan

大象thinking in uml电子版

大象thinking in uml epub

thinking in java练习题

thinking in c++ 英文版

thinking in uml pdf

最新资源