C#编程思维指南：从入门到高级特性

需积分: 1 68 浏览量更新于2024-07-22 收藏 4.5MB PDF 举报

《Thinking in C#》是Larry O'Brien和Bruce Eckel合作编写的一本深入讲解C#编程语言的书籍，由Prentice Hall出版，发行于Upper Saddle River, New Jersey。本书旨在帮助读者理解和掌握C#编程思想，特别适合那些希望进一步提升C#技能或者初次接触C#的程序员。书中的内容涵盖了一系列关键主题，包括但不限于： 1. **计算机语言概览**：首先介绍了学习C#的背景和必要性，让读者了解这门语言在编程领域的位置。 2. **对象导向编程入门**：通过实例阐述面向对象编程的基本概念，如类（Class）、对象（Object）和方法（Method），让读者掌握C#中的核心构造。 3. **Hello, Objects**：章节深入到如何创建、实例化和操作对象，强调实践的重要性。 4. **控制程序流程**：涉及条件语句、循环、异常处理等内容，使读者学会如何控制代码的执行路径。 5. **初始化与清理**：介绍如何初始化对象和正确管理资源的生命周期，确保程序的稳健性。 6. **隐藏实现细节**：探讨封装（Encapsulation）和访问修饰符，如何保护数据和方法的私有性。 7. **类的重用与接口**：理解如何设计可复用的类和接口，提高代码的可扩展性和模块化。 8. **耦合与内聚**：分析代码之间的关系，强调降低依赖性和提高代码结构的紧密度。 9. **对象的收集与错误处理**：讨论垃圾回收机制以及如何有效地处理程序运行时可能出现的错误。 10. **输入/输出（I/O）操作**：介绍C#中的I/O操作，包括文件操作、网络通信等基本功能。 11. **反射和元数据**：展示如何通过反射API探索和修改程序的运行时结构。 12. **Windows Forms编程**：教授使用C#构建图形用户界面（GUI）的基本知识。 13. **GDI+概述**：图形设备接口（GDI+）在C#中的应用，用于图形和图像处理。 14. **多线程编程**：指导读者如何在C#中实现并发和并行处理，提高程序性能。 15. **XML**：讲解如何使用C#处理和创建XML文档，以及与XML相关的工具和技术。 16. **Web编程**：介绍C#在Web开发中的应用，包括ASP.NET框架的基础。 17. **针对不同背景的指南**：专门针对那些来自其他编程语言（如Visual Basic或Java）的读者提供转换和迁移建议。 18. **测试驱动编程和NUnit**：推荐使用测试驱动开发（TDD）方法，以及如何使用NUnit进行单元测试。 19. **移动开发**：探讨在Pocket PC上使用C#进行应用程序开发的可能性。 20. **编程最佳实践**：提供C#编程的实用建议，帮助读者写出高效、可维护的代码。 21. **索引与附录**：详尽的索引和参考文献，便于查找特定主题。《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页未读，继续阅读

doctorx4587

粉丝: 2
资源: 28

C#编程思维指南：从入门到高级特性

Thinking_In_C#英文正式版

Thinking_in_CSharp

think in c#英文版

thinking_轨迹规划_航行轨迹_基于los无人水面艇的路径跟踪_own3oh_水面无人艇

thinking in linq中文

thinking in patterns 百度百科

thinking in uml pdf 电子书

thinking in c++ 中文版 pan

大象thinking in uml epub

大象thinking in uml电子版

最新资源