Windows Forms 2.0数据绑定：构建智能客户端数据应用

1星需积分: 10 68 浏览量更新于2024-07-23 收藏 10.89MB PDF 举报

"Data Binding with Windows Forms 2.0: Programming Smart Client Data Applications with .NET" 本书《Data Binding with Windows Forms 2.0》由Brian Noyes撰写，旨在深入探讨Windows Forms 2.0中的数据绑定技术，帮助开发者创建智能客户端数据应用程序。Brian Noyes是一位软件架构师、培训师、作家和演讲者，他在IDesign公司担任首席架构师，该公司的业务主要涉及.NET架构和设计咨询与培训。他有着超过十五年的软件系统开发经验，同时也是全球多个重要软件会议的演讲嘉宾，并在各种软件期刊和杂志上发表文章。该书于2006年由Addison Wesley Professional出版社出版，具有ISBN-10：0-321-26892-X和ISBN-13：978-0-321-26892-1，共736页，包含目录和索引。书中，Brian Noyes以吸引人的写作风格详细阐述了数据绑定的各个方面。他以简单易懂的方式引导读者了解每个主题，然后逐步深入到实际应用和可扩展性策略中。特别是，当讨论数据绑定架构、使用模式、数据集的价值、控件绑定等时，Brian Noyes会明确地给出他的推荐建议。这本书不仅适合.NET 2.0的新手，也适合有一定经验的开发者。对于关心应用程序中数据处理的任何人（几乎可以说所有开发者），阅读此书都将收获新的知识和实用技巧。书评人Michele Leroux Bustamante，既是IDesign的首席架构师，也是微软区域总监和MVP，高度评价了这本书。她认为，无论你是.NET新手还是有经验的开发者，都能从这本书中找到有价值的内容，学习到新的、有用的数据处理方法。本书的内容涵盖了： 1. 数据绑定基础：解释数据绑定的基本概念，如何将数据源与用户界面元素关联。 2. Windows Forms 2.0的增强：介绍新版本中对数据绑定的支持和改进。 3. 数据集和数据适配器：探讨如何使用DataSet和DataAdapter进行数据操作和缓存。 4. 控件绑定：讲解如何将数据绑定到各种Windows Forms控件，如TextBox、ListBox和DataGridView等。 5. 数据绑定架构：深入研究数据绑定的设计模式和最佳实践。 6. 动态数据绑定：介绍如何实现动态数据源和响应数据变化的机制。 7. 数据验证：讨论数据输入验证的重要性以及实现方法。 8. 错误处理和异常处理：阐述如何处理数据绑定过程中可能出现的问题。 9. 扩展性：探讨如何设计可扩展的数据绑定解决方案，以适应不断变化的需求。通过这些内容，读者将能够构建出强大且灵活的智能客户端数据应用，利用.NET框架的强大功能来优化数据操作和用户体验。

Conventions

Developing applications is more about tools and less about code. However, there is a lot of

code in this book, and I have adopted some common conventions to help make things easier.

References to classes, variables, namespaces, and other artifacts that manifest themselves in

code are in a

monospace

font; this helps you distinguish an instance of the

DataSet

class from a

conceptual discussion of data sets. Short code listings are presented inline within the text

using a different

monospace

font:

private void Form1_Load(object sender, EventArgs e)

{

m_EmployeesTableAdapter.Fill(northwindDataSet.Employees);

}

Longer listings use a similar font, but are identified with listing numbers, for example, Listing

4.1. Within code listings,

bold

highlights particularly relevant portions of the code, especially

"evolving code." When I remove details that aren't relevant to a discussion, you'll see a

comment with an ellipsis (

//...

). This means that more code is needed to complete the

example or more code generated by the designer exists, but you don't need it to understand

the concept. On occasion, explanatory comments show context:

public partial class CustomersDataSet : System.Data.DataSet {

// ...

// Nested typed DataTable definition

public partial class CustomersDataTable : System.Data.DataTable,

System.Collections.IEnumerable {

// Strongly typed indexer for accessing rows

public CustomersRow this[int index] { ... }

// ...

}

I use a conversational tone to discuss the kinds of objects you deal with in data-binding

scenarios, for example, when describing the

DataSet

class in this book. However, much of the

time when discussing data sets I am not talking about an instance of a

DataSet

class, but of

an instance of a derived typed

DataSet

class. Although it would still be technically correct to

refer to that class as a

DataSet

because it "is a"

DataSet

tHRough inheritance, I find it

annoying when too many words are called out as a code artifacts. So, when something really

is a code artifact and can only be discussed correctly in that context, it's set in the

monospace

font. I favor the terms data set, data table, and table adapter when discussing concepts

surrounding those types of objects, and reserve

DataSet, DataTable

, and

CustomersTableAdapter

for citing a specific class type or instance, and the capabilities defined

by that code artifact.

Discussing components and controls can also be confusing, depending on how precise you

want to be with your language. Technically, all controls in Windows Forms are components,

because the

Control

class derives from the

Component

class. Many of the concepts surrounding

data binding apply to both components, such as the

BindingSource

component discussed in

depth in this book, and controls, such as a

DataGridView

control. Unfortunately, many people

think of components as nonvisual objects that are used by your form and controls as objects

that have a visual rendering on your forms. To avoid having to say controls and components

ad nauseam, when I discuss a concept that applies to both nonvisual components and

controls, I simply say components. So when you see components, think "this applies to

controls as well, because they inherit from components."

Page 16

ABC Amber CHM Converter Trial version, http://www.processtext.com/abcchm.html

System Requirements

This book was written with the code base of .NET 2.0 and Visual Studio 2005 over the course

of Beta 1, several Community Technical Previews, and ultimately Beta 2. The code presented

in this book runs with Beta 2. I worked closely with the Windows Client product team at

Microsoft, and there are no feature changes planned between Beta 2 and product release.

However, some minor syntax may change between production and the release of .NET 2.0. If

they do affect the code or concepts, I will provide corrections through the Web site for the

book (www.softinsight.com/databindingbook), as well as updated code that will run on Visual

Studio 2005 once it is released.

If you plan to run the samples available on the book's Web site, or the walkthroughs and code

listings in the book, you will need Visual Studio 2005 installed on your machine, and you will

need access to a SQL Server 2000 or 2005 database server on which the Northwind sample

database has been installed. Additionally, you will need to have permissions on that database

to create new databases for some of the samples.

There are multiple versions of Visual Studio 2005 to choose from. All of the features discussed

in this book even work in the Express versions of Visual Studio 2005, which are free. You can

develop all of the samples in this book in Visual C# 2005 Express or Visual Basic 2005 Express

with SQL Server 2005 Express, but because Express versions of Visual Studio don't support

data connections using server paths (they only support file path-based connections to SQL

Express databases), you will have to create the sample databases and data in SQL Express,

and then alter the connection strings and the way you set up connections based in Express.

The samples and scripts included in the book assume you are working on a machine with a

standard, professional, or enterprise version of Visual Studio 2005 installed, along with a

default instance of either SQL Server 2000 or 2005 on your local machine. To run the samples

without that configuration will require modifying the connection string settings for all of the

samples that run against a database. The modifications needed are discussed on the book's

Web site, and the differences in connection strings are highlighted in many places in the

sample code.

Additionally, Northwind doesn't ship with SQL Server 2005, but is available as a separate

installable download that will work with SQL Server 2005 from MSDN Downloads at

www.microsoft.com/downloads/details.aspx?FamilyID=06616212-0356-46A0-8DA2-EEBC53A68

034&displaylang=en. The download provides scripts and MDF files that can be attached to

SQL Server 2005 or used with SQL Server 2005 Express.

Page 18

ABC Amber CHM Converter Trial version, http://www.processtext.com/abcchm.html

Coding Standards

Yes, I have coding standards, and you should too. It is as simple as that, but unfortunately

not done nearly enough by development organizations. Coding standards are an important tool

in making sure that code is bug free, but they are even more essential for making sure that

your code base is maintainable. Code written by one developer on your team should look like

the code written by all the other developers so that it can be maintained and extended if

necessary. Code reviews go hand-in-hand with your coding standard and are also something

that should be a regular part of your development process.

We have an excellent coding standard at IDesign, which can be downloaded from our site at

www.idesign.net. You can use as is, or you can use it to develop your own coding standard.

Our standard includes a lot of information that goes beyond simple syntax; it has a lot of best

practices for .NET development and design.

For the code presented in this book, I used the IDesign coding standard for naming member

variables, properties, methods, and event handlers. Any member of a class, whether just a

variable or a control on a form, is given a prefix of m_ and PascalCasing is used for the rest of

the name. This is different from the Microsoft standard (which varies somewhat across

different product teams), and that is okay. You can use whatever standard you want, as long

as you are consistent. I won't go into the arguments and justifications of coding standard

here, but I want to short-circuit any complaints or e-mails that might result.

You will see code snippets where this convention isn't followed (when I am discussing

designer-generated code), because the naming conventions generated by the designer differ

from our coding standard. So when discussing the raw code generated by the designer, I will

demonstrate the way they generate the code; when I am writing code or focusing on other

aspects of the code, I will rename the things generated by the designer to comply with

IDesign coding standard.

Page 20

ABC Amber CHM Converter Trial version, http://www.processtext.com/abcchm.html

剩余651页未读，继续阅读

theFates

粉丝: 2
资源: 27

Windows Forms 2.0数据绑定：构建智能客户端数据应用

Data Binding with Windows Forms 2.0 Programming

Data Binding with Windows Forms 2.0 Programming Smart Client Data Applications with .NET

Data Binding with Windows Forms 2.0

Windows Forms 2.0 程序设计.PDF

WINDOWS FORMS 2.0数据绑定--.NET智能客户端数据应用程序设计(英文pdf)

[Brian_Noyes]_Data_Binding_with_Windows_Forms_2.0.chm.zip

Windows Forms Programming with C#

WPF Data Binding with LINQ to SQL

RSS-XML Data-Binding to Data Control with Row Limitations

Android Data Binding

最新资源