|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
WPF Data Binding with LINQ to XML Overview
This topic introduces the dynamic data binding features in the System.Xml.Linq namespace. These features can be used as a data source for user interface (UI) elements in the Windows Presentation Foundation (WPF).
The Extensible Application Markup Language (XAML) is an XML dialect created by Microsoft to support .NET Framework 3.0 technologies. It is used in WPF to represent user interface elements and related features, such as events and data binding. In Windows Workflow Foundation, XAML is used to represent program structure, such as program control (workflows). XAML enables the declarative aspects of a technology to be separated from the related procedural code that defines the more individualized behavior of a program.
There are two broad ways that XAML and LINQ to XML can interact:
Because XAML files are well-formed XML, they can be queried and manipulated through XML technologies such as LINQ to XML.
Because LINQ to XML queries represent a source of data, these queries can be used as a data source for data binding for WPF UI elements.
This documentation describes the second scenario.
WPF data binding enables a UI element to associate one of its properties with a data source. A simple example of this is a Label whose text presents the value of a public property in a user-defined object. WPF data binding relies on the following components:
The UI element to be associated with the data source. Visual elements in WPF are derived from the UIElement class.
The dependency property of the binding target that reflects the value of the data-binding source. Dependency properties are directly supported by the DependencyObject class, which UIElement derives from.
The source object for one or more values that are supplied to the UI element for presentation. WPF automatically supports the following types as binding sources: CLR objects, ADO.NET data objects, XML data (from XPath or LINQ to XML queries), or another DependencyObject.
The property of the binding source that resolves to the value or set of values that is to be bound.
A dependency property is a concept specific to WPF that represent a dynamically computed property of a UI element. For example, dependency properties often have default values or values that are provided by a parent element. These special properties are backed by instances of the DependencyProperty class (and not fields as with standard properties). For more information, see Dependency Properties Overview.
Dynamic Data Binding in WPF
By default, data binding occurs only when the target UI element is initialized. This is called one-time binding. For most purposes, this is insufficient; typically, a data-binding solution requires that the changes be dynamically propagated at run time using one of the following:
One-way binding causes the changes to one side to be propagated automatically. Most commonly, changes to the source are reflected in the target, but the reverse can sometimes be useful.
In two-way binding, changes to the source are automatically propagated to the target, and changes to the target are automatically propagated to the source.
For one-way or two-way binding to occur, the source must implement a change notification mechanism, for example by implementing the INotifyPropertyChanged interface or by using a PropertyNameChanged pattern for each property supported.
For more information about data binding in WPF, see Data Binding.
Most LINQ to XML classes do not qualify as proper WPF dynamic data sources: Some of the most useful information is available only through methods (and not properties), and properties in these classes do not implement change notifications. To support WPF data binding, LINQ to XML exposes a set of dynamic properties.
These dynamic properties are special run-time properties that duplicate the functionality of existing methods and properties in the XAttribute and XElement classes. They were added to these classes solely to enable them to act as dynamic data sources for WPF. To meet this need, all these dynamic properties implement change notifications. A detailed reference for these dynamic properties is provided in the next section, LINQ to XML Dynamic Properties.
Many of the standard public properties, found in the various classes in the System.Xml.Linq namespace, can be used for one-time data binding. However, remember that neither the source nor the target will be dynamically updated under this scheme.
Accessing Dynamic Properties
Accessed directly at compile time. Dynamic properties are invisible to the compiler and to Visual Studio IntelliSense.
Discovered or accessed at run time using .NET reflection. Even at run time, they are not properties in the basic CLR sense.
In C#, dynamic properties can only be accessed at run time through facilities provided by the System.ComponentModel namespace.
In contrast, however, in an XML source dynamic properties can be accessed through a straightforward notation in the following form:
The dynamic properties for these two classes either resolve to a value that can be used directly, or to an indexer that must be supplied with an index to obtain the resulting value or collection of values. The latter syntax takes the form:
For more information, see LINQ to XML Dynamic Properties.