Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Type Converters and Markup Extensions for XAML

Type converters and markup extensions are two techniques that XAML type systems and XAML writers use to generate object graph components. Although they share some characteristics, type converters and markup extensions are represented differently in a XAML node stream. In this documentation set, type converters, markup extensions, and similar constructs are sometimes collectively referred to as value converters.

This topic contains the following sections.

In XAML, value converters are used for various scenarios. The following list shows the different types of value converters in XAML:

  • Type converter

  • Markup extension

  • Value serializer

  • Related class or support class that provides the logic for a XAML text syntax

In the .NET Framework XAML Services definition, type converters are classes that derive from the CLR TypeConverter class. TypeConverter is a class that was in the Microsoft .NET Framework before XAML existed. Its original purpose was to support property windows and similar text-based editing metaphors for IDE properties. The introduction of XAML to .NET Framework uses TypeConverter to convert a text syntax (as found in an attribute value or a XAML value node) into an object. TypeConverter can also be used to serialize an object value to text syntax. TypeConverter was also used in previous framework-specific XAML implementations in Windows Presentation Foundation (WPF) and Windows Communication Foundation (WCF). For more information about the TypeConverter in XAML, see Type Converters for XAML Overview.

In the .NET Framework XAML Services implementation, markup extensions are classes that derive from the MarkupExtension class. Markup extensions are a concept that in this form is originated by the XAML language. You can think of a markup extension as being something like an extensible escape sequence that calls into a service class to provide its logic. In terms of markup, XAML processors universally recognize a markup extension by a text sequence that starts with an opening brace ({) in a text string.

Markup extensions differ from type converters. Type converters are typically associated with types or members. They are invoked when an object graph creation or a serialization encounters text syntax that is associated with those entities.

Markup extensions are associated with a single supporting service class, but can be applied for any member value. (However, you can implement your markup extension to deliberately restrict its use to certain members or destination types, by using service context.) Markup extensions can override a type converter association. Or you can use them to specify an attribute value for members that would not otherwise support a text syntax.

For more information about the markup extension implementation pattern for XAML, see Markup Extensions for XAML Overview.

NoteNote

The MarkupExtension and ValueSerializer types are both in the System.Windows.Markup namespace and not in the System.Xaml namespace. This does not imply that these types are specific to either the WPF or Windows Forms technologies that otherwise populate CLR namespaces that contain the string Windows. MarkupExtension and ValueSerializer are in the System.Xaml assembly and have no specific framework dependency. These types existed in the CLR namespace for .NET Framework 3.0 and remain in the CLR namespace in .NET Framework 4 to avoid breaking references in existing WPF projects. For more information, see Types Migrated from WPF to System.Xaml.

A ValueSerializer is a specialized type converter that is optimized for converting an object to a string. A ValueSerializer for XAML might not implement the ConvertFrom method at all. A ValueSerializer implementation obtains services in a manner that is like a TypeConverter implementation. The virtual methods provide an input context parameter. The context parameter is of type IValueSerializerContext, which inherits from the IServiceProvider interface and has a GetService method.

In the XAML type system and for XAML writer implementations that use XAML node loop processing for serialization, a value converter that is associated with a type or member is reported by its own XamlType.ValueSerializer property. The meaning to XAML writers that perform serialization is that if a XamlType.TypeConverter and XamlType.ValueSerializer exist, the type converter should be used for the load path and the value serializer should be used for the save path. If XamlType.TypeConverter exists but XamlType.ValueSerializer is null, the type converter is also used for the save path.

A value converter is extensible beyond the specific patterns of a type converter or a markup extension. However, this customization would also require the redefinition of the XAML type system as provided by .NET Framework XAML Services. The existing XAML type system has representations and reporting systems for type converters, markup extensions, and value serializers, but not for custom forms of value conversion. If you want to create custom value converters, use the XamlValueConverter<TConverterBase> type.

Markup extensions and type converters are used for different situations in XAML. Although context is available for markup extension usages, type conversion behavior of properties where a markup extension provides a value is generally is not checked in the markup extension implementations. In other words, even if a markup extension returns a text string as its ProvideValue output, type conversion behavior on that string as applied to a specific property or property value type is not invoked. Generally, the purpose of a markup extension is to process a string and return an object without any type converter involved.

When you implement a value converter, you often need access to a context in which the value converter is applied. This context is known as the service context. The service context might include information such as the active XAML schema context, access to the type mapping system that the XAML schema context and XAML object writer provide, and so on. For more information about the service contexts available for a value converter and how to access the services that a service context might provide, see Service Contexts Available to Type Converters and Markup Extensions.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.