C#编程思维指南：面向对象与实践

5星 · 超过95%的资源需积分: 10 186 浏览量更新于2024-07-29 收藏 4.5MB PDF 举报

《C#编程思想 Thinking In C#》是由Larry O'Brien和Bruce Eckel共同编著的一本深入解析C#编程语言的权威著作，隶属于Bruce Eckel的经典编程思想系列丛书。本书旨在帮助读者理解C#的核心概念，通过实例讲解，引导读者掌握从基础到高级的编程技巧。在本书的开篇，作者首先介绍计算机语言的历史背景，强调了C#在现代软件开发中的重要地位，以及它如何适应不断发展的技术环境。第1章"Those Who Can, Code" 强调了编程能力的价值，并鼓励初学者投身于C#的世界。接下来，作者逐步引导读者进入对象导向编程的世界。第2章"Introduction to Objects"阐述了类、对象和封装的基本概念，让读者对面向对象编程有初步认识。在第3章"Hello, Objects"，读者将学习如何创建和操作简单的类和对象，以及继承和多态的基础。第4章"Controlling Program Flow"讨论控制流的关键元素，如条件语句、循环和函数，帮助读者构建程序的逻辑结构。随后的章节深入探讨了初始化与清理（Chapter 5）、隐藏实现细节（Chapter 6）以及类的重用（Chapter 7），这些都是提高代码效率和可维护性的重要课题。 C#的设计原则和接口与实现的关系在第8章"Interfaces and Implementation"中被详细剖析，帮助读者理解和实践接口编程。第9章"Coupling and Cohesion"涉及软件设计中的耦合度和内聚度，强调模块化设计的重要性。随着内容的推进，第10章"Collecting Your Objects"涉及垃圾回收机制，让读者了解内存管理在C#中的工作方式。第11章"Error Handling with Exceptions"讨论异常处理，确保程序在遇到错误时能够优雅地恢复。第12章和第13章分别聚焦I/O操作和反射与元数据，前者介绍如何进行输入输出操作，后者展示了如何动态获取和修改程序运行时的信息。第14章"Programming Windows Forms"是针对Windows应用程序开发的详尽教程，而第15章的GDI+概述则涵盖了图形用户界面设计的基础。对于已经熟悉其他语言的读者，书后还提供了专门章节，如A章"C# for Visual Basic Programmers"和B章"C# for Java Programmers"，便于不同背景的人对比学习。此外，第16章和第17章分别涉及多线程编程和XML技术，现代软件开发中不可或缺的技能。第18章"Web Programming"深入讲解Web开发，包括ASP.NET和相关的Web服务。书尾还包含一些附录，如为Visual Basic开发者准备的转换指南、C#编程最佳实践、资源推荐，以及索引和术语表，方便读者查找和回顾关键知识点。《C#编程思想 Thinking In 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页未读，继续阅读

阿苍

粉丝: 6
资源: 2

C#编程思维指南：面向对象与实践

C#编程思想(Thinking in C#)

Thinking In C#(C#编程思想英文)

C#入门经典和C#编程入门与应用的区别

有什么C#编程的图书和B站视频推荐给零基础的财务人，财务人学C#的学习路线，学习之前还需要学习哪些编程呢

有没有C#可编程的开发板

halcon联合c#编程

halcon c#联合编程

零基础学习VB编程和C#编程有没有先后顺序

雷赛运动控制卡结合C#编程案例

C#编程作为OPC Server服务器以供他人连接

最新资源