A XAML namescope stores relationships between the XAML-defined names of objects and their instance equivalents. This topic describes the implications of the XAML namescope concept on how you might compose your XAML and interact with the run-time object tree.
Explains the presence and purpose of the two XML namespace (xmlns) mappings as found in the root element of most Silverlight XAML files. It also describes how to produce similar mappings for using elements that are defined in your own code and/or within separate assemblies.
Explains how to use the XamlReader.Load method, provides requirements for the input XAML, explains how to connect the output to the object tree, and discusses the XAML namescope issues that can affect using the FindName method against parts of the object tree that originated from a call to XamlReader.Load.
The TypeConverter class serves a particular purpose as part of the Silverlight implementation of XAML attribute value processing. This topic explains the role of TypeConverter and provides guidance for writing your own TypeConverter for custom XAML attribute usages.
Describes some of the conventions that are found in the XAML usage syntax, and provides links to other topics that can help you understand XAML language concepts and how they relate to XAML usage and the Silverlight documentation.
Describes the concepts of the default Silverlight XAML namespace and the reason why you might need to create mappings for additional XAML namespaces when you define parts of a Silverlight-based application in XAML.