For example, you can set up
an event handler that responds to the Click event of every button in a window. Chapter 6 has more
about this technique.
??? Defining resources. Resources are objects that you define once in your XAML and in a special section
of your XAML and then reuse in various places in your markup. Resources allow you to centralize and
standardize formatting, and create nonvisual objects such as templates and animations. Chapter 11
shows how to create and use resources.
??? Defining control templates. WPF controls are designed to be lookless, which means you can substitute
your custom visuals in place of the standard appearance. To do so, you must create your own
control template, which is nothing more than a block of XAML markup. Chapter 15 tackles control
templates.
??? Writing data binding expressions. Data binding allows you to extract data from an object and display
it in a linked element. To set up this relationship and configure how it works, you must add a data binding
expression to your XAML markup. Chapter 16 introduces data binding.
??? Defining animations. Animations are a common ingredient in XAML applications. Usually, they??™re
defined as resources, constructed using XAML markup, and then linked to other controls (or triggered
through code). Currently, Visual Studio has no design-time support for crafting animations.
Pages:
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114