精通WPF 4实战：从入门到企业级应用

需积分: 10 4 浏览量更新于2024-07-22 收藏 4.49MB PDF 举报

"Apress的《Applied WPF 4 in Context》是一本深入介绍Windows Presentation Foundation (WPF) 4的实用指南。该书旨在帮助读者在Windows系统环境下开发丰富的客户端应用程序，充分利用WPF的强大功能。全书共分为14章，内容涵盖了从入门到进阶的核心主题。第1章"Introducing WPF and XAML" 引导读者了解WPF的基本概念和XAML语言，这是构建用户界面的基础。XAML (Extensible Application Markup Language) 是一种声明式编程语言，允许设计师定义应用程序的布局和样式。第2章至第5章着重于实际应用，"Sample Application: Overview and Getting Started" 概述了一个示例应用的架构，并引导读者进行初步的开发。随后的章节分别介绍了如何使用Microsoft Expression Blend 进行设计、创建视图(Views)，以及如何添加控件和处理数据绑定。第6章深入探讨了"The Entity Framework"，讲解如何在WPF应用中集成ORM（对象关系映射），以管理和操作数据库。数据绑定在第7章"Data Binding"中被详细讨论，它是WPF中的关键机制，实现了数据与用户界面的自动同步。第8章"Command Handling and Event Routing" 讨论了命令处理和事件路由，这是实现用户交互和应用程序逻辑的重要部分。第9章"Testing with TDD" 则强调了测试驱动开发(TDD)在WPF项目中的应用，保证代码质量和可维护性。第10章介绍了"Report with Microsoft Reporting Services"，展示了如何利用Microsoft Reporting Services生成专业报告，扩展应用的功能。第11章"Deploy the Application Using ClickOnce" 教授如何使用ClickOnce轻松部署WPF应用程序，简化了发布流程。第12章至第14章关注高级主题："Design Patterns in WPF" 探讨了在WPF中运用设计模式，提升代码结构和性能；"WPF and Multithreading" 讲解多线程编程在WPF中的应用，确保并发操作的效率；最后，"Interacting with WCF" 展示如何通过Windows Communication Foundation (WCF) 实现与服务端的通信，实现前后端分离。《Applied WPF 4 in Context》不仅提供了技术细节，还注重实践和案例分析，是WPF开发者不可多得的参考书籍，无论你是初学者还是经验丰富的开发人员，都能从中收获宝贵的知识和技能。"

CHAPTER 1 ■ INTRODUCING WPF AND XAML

• Grid: Defines a table-style container with rows and columns and acts like an

HTML table where you can span controls across multiple rows and columns.

• StackPanel: A container that stacks the controls vertical or horizontal one after the

other one. You can define the space between each control.

• WrapPanel: Positions child elements in sequential position from left to right,

breaking content to the next line at the edge of the containing box.

In WPF you have the same layout logic described in HTML by the box model technique where each

control has a Margin property and each child has a Margin property and a Padding property.

Margin defines the space between an element and its child elements. Padding defines the space

between a child element and its parent container. The main difference between the two properties is

that Margin gives you space outside the control, and Padding gives you space inside the control.

Additional position properties are HorizontalAlignment and VerticalAlignment, which are used to

specify a default position of a control in the container.

Figure 1-3 shows a summary overview of the position techniques in WPF.

Figure 1-3. WPF controls position overview

Common Controls

WPF offers a set of common controls available in the Visual Studio toolbox that can be used for your

daily activities without the need of writing additional code. In some cases, you may need to customize

the appearance of a control or to change the behavior of a control using the styles and the templates.

In other cases, you may need to listen for an event of a control in order to execute a specific code; for

example, you may need to listen for the Click event of a Button control in order to execute a specific

operation.

CHAPTER 1 ■ INTRODUCING WPF AND XAML

All these steps can be accomplished using the XAML markup or by writing code-behind the XAML; it

depends on what you are doing and how you are doing it. In this section, you will see the available

controls provided by XAML, and in the next chapters, you will see how you can customize the default

appearance and the default behaviors of a control.

Control Composition

Each control that inherits from the base class System.Windows.Controls.Control is composed by a

default set of components that you can customize and change using the StyleTemplate or the

DataTemplate. The class Control is composed by a ControlTemplate, which represents the default

template for the appearance of the control in the UI; when you customize the DataTemplate of a control,

you change how the ControlTemplate should behave.

The ControlTemplate may display a single item, a collection of items (like a ListBox), or a Header of

an item; for this reason, in WPF you have controls that are of type ContentControl, ItemsControl, or

HeaderControl based on how the ControlTemplate should be structured.

Visual Studio and the .NET Framework 4 provide a set of default controls, detailed in the following

list. If you want to get a more detailed explanation of each control, refer to http://msdn.microsoft.com/

en-us/library/system.windows.controls.aspx, in particular to the section “System.Windows.Controls”

where you will find the complete list of available controls.

The following are the categories of available controls in .NET 4; they represent only part of the full

set of controls delivered with the .NET Framework 4.

• Buttons: This represents a Button with a label or complex content.

• Inputs: TextBlock and TextBox are part of the available input controls; the first

control can be used as a Label, while the second control is used to retrieve or

display text in the UI.

• List: GridView, ListBox, ComboBox, and ItemsControl are controls able to display

and select items in a list of items.

• Layout: This section consists of all the controls designed to contain and provide

layout to child controls, such as StackPanel, DockPanel, and so on.

• Documents: These are controls designed for interacting with documents such as

XPS documents.

As I said previously, every one of these controls can be added to the UI using two different

approaches: you can declare the control by using XAML or by writing C# code and adding the control to

the controls collection of the parent container. Listing 1-7 shows the two methods.

Listing 1-7. Example of Creating a C

ontrol with XAML or with C#

</StackPanel>

CHAPTER 1 ■ INTRODUCING WPF AND XAML

redirect the call to the UI thread. The Dispatcher provided in this namespace is in charge of solving this

problem.

System.Windows.DependencyObject is another class fundamental in WPF; it enables the tracking

process of the dependencies of a property of a XAML object. For example, when you data bind an object

to a view, in XAML DependencyObject acts as a mediator between the view and the Bind object and

notifies the two actors when something changes.

System.Windows.Media.Visual is the namespace in charge of controlling the way the UI is designed

and the way the pixels are rendered on the screen. This assembly is not used directly by you, but it is

used indirectly when you create, for example, a new control in the UI.

In System.Windows.UIElement, you can find everything related to layout, input, and events. In the

layout, as you saw in the previous section, you will find all the controls in charge of arranging the

elements in the UI; in the input and events, you will find all those methods useful to control the user

interaction such as MouseClick or SelectionChanged.

In System.Windows.FrameworkElement, you can find part of the UI properties used to manage the

layout, such as HorizontalAlignment and VerticalAlignment for example, or the data binding engine and

the styles.

Finally, System.Windows.Controls is the namespace in charge of providing everything for the

creation of UI controls; it also contains all the UI controls shipped with WPF 4.

These are the namespace available in WPF that provide all the tools and mechanisms to make a

consistent and powerful WPF application; in the course of this book, you will see when and how to use

most of them.

Technologies

In the previous section, you saw that WPF ships with a set of assemblies, and each one provides one or

more WPF-related technologies such as styles, data binding, commanding, and more. In this section,

you’ll get an overview of the technologies provided with this set of assemblies and how to use them and,

more than anything else, why they are useful.

Styles

If you ever worked in the past with any web technology such as ASP.NET, PHP, JSP, or even a simple

HTML web page, you may know that every part of a web page can be styled using Cascading Style Sheets

(CSS). In this way, you can create a UI style to represent a TextBox in a particular way, and this style will

be spread all over you web application.

If you ever worked before with a client technology such as Windows Forms or Java Forms, you may

know that this is an impossible task to achieve using the basic tools provided by these two frameworks.

What I mean is that in Windows Forms, you can’t define a style for a UI control; you need to create a

specific UI control that has the style hard-coded in the base class. For example, if you want a nice

TextBox with a specific border color and a specific border shape, in Windows Forms you have to create a

custom TextBox.

In WPF you have the styles like you have on the Web, but probably with a lot more power and

control. In a style you can set static values or dynamic values using triggers; for example, you may have a

TextBox style that defines the background color to white, but when the TextBox gets the focus, the

background becomes yellow.

Listing 1-8 shows how you set up some properties on a TextBox using the TextBox element itself or

using an embedded style in the Resource property of the parent element.

CHAPTER 1 ■ INTRODUCING WPF AND XAML

Listing 1-8. Comparison Between Embedded Setter or Style

<StackPanel.Resources>

</Style>

</StackPanel.Resources>

<TextBox Width="200" Height="25"

FontFamily="Tahoma" FontSize="12" />

</StackPanel>

In the second case, you can easily recycle and apply the property Style="{StaticResource

TxtStyle}" to any TextBox and spread your style all over the application.

The only constraint you have when you prepare a style for a specific control is that the style must be

for a specific control, and to do that, you must provide a value for the property TargetType of the Style

element; in this property, you have to specify the control you are styling.

Additional consideration has to be done to the x:Key attached property. If you specify a key, you

must provide that key on every control that has to use the style; otherwise, you can avoid specifying a

value for the x:Key property so that any control of that type will use the style.

Data Templates

Another way to customize the layout of your controls is using the DataTemplates. A DataTemplate is the

template that represents the data exposed by your control. Usually you work with a DataTemplate when

you want to customize how an ItemsControl displays its items at runtime, but you can use the

DataTemplate also to customize a control that displays a single item. Usually, an ItemsControl, like a

ListBox, displays the .ToString() method of the items bound to it in the UI, so when you try to bind a

list of objects to a List control, you will get a weird result, and the only property available to customize

the data you are displaying is the DisplayMemberPath, which allows you to prompt only one property by

using a string format. If you customize the DataTemplate of your ListBox, you will be able to visualize

the items bound to the control as you want them; for example, you may force the ListBox to display for

each row the FirstName and the LastName of a Person class in a StackPanel using two TextBlock controls.

Figure 1-5 shows a screenshot of Visual Studio 2010; in the figure there is a UserControl with two

ListBox controls bound to the same data source, which is a List<T> of class Person. As you can see, the

first ListBox shows the full name of the object bound to the ListBox, while the second ListBox is using

the DataTemplate tocustomize the way the data is displayed in the ListBox.

剩余346页未读，继续阅读

lsb0733

粉丝: 1
资源: 54

精通WPF 4实战：从入门到企业级应用

Illustrated WPF

Applied WPF 4 in Context.pdf

Applied WPF 4 In Context

Apress.Applied.WPF.4.in.Context.2011

Apress.Applied.ASP.NET.4.in.Context.2011

Apress.Pro.WPF.Windows.Presentation.Foundation.in.dot.NET.3.0.May.2007.pdf

Applied WPF 4 in Context

Apress.Foundations.of.WPF.Nov.2006.pdf

Apress.WPF.Recipes.in.C.Sharp.2008.A.Problem.Solution.Approach.Nov.2008

【英文版】Apress.Pro.WPF.and.Silverlight.MVVM.pdf

最新资源