Familiarize yourself with the XAML language specs
"The Microsoft Extensible Application Markup Language (XAML) technical documentation set provides preliminary technical specifications for this language based on Extensible Markup Language (XML) that enables developers to specify a hierarchy of objects.
- [MS-SLXV].pdf, 2.7 MB Download
- [MS-SLXV-2010].pdf, 4.2 MB Download
- [MS-VBAL].pdf, 3.7 MB Download
- [MS-WPFXV].pdf, 9.2 MB Download
- [MS-WPFXV-2010].pdf, 12.0 MB Download
- [MS-WPFXV-2012].pdf, 12.7 MB Download
- [MS-XAML].pdf, 2.8 MB Download
- [MS-XAML-2009].pdf, 2.6 MB Download
- [MS-XAML-2012].pdf, 2.6 MB Download
- MicrosoftComputerLanguages.zip, 34.6 MB Download
The XAML technical documentation set provides detailed preliminary technical specifications of XAML Object Mapping. This documentation set includes details on XAML’s data model for Types, XAML’s data model for object hierarchies, and the techniques with which one maps from XML to those object hierarchy data model. Also included is documentation of Windows Presentation Foundation’s (WPF) set of Types and of the Silverlight Vocabulary of Types that can be used in conjunction with XAML.
The XAML preliminary technical documentation set is intended for use in conjunction with publicly available standard specifications, network programming art, and Windows distributed systems concepts. It assumes that the reader either is familiar with this material or has immediate access to it.
The technical documentation set provides the following levels of audience support:
- Implementer: Sufficient conceptual and reference information for a successful implementation of one or more protocol specifications for a given task or scenario.
- Reviewer: A definitive resource for readers who want to evaluate or understand one or more protocols.
Not sure if I've seen the XAML language specification, and it's variants, distributed like this before (I'm sure it has been, but I've missed it). In any case, I thought this really kind of cool, so there... :)
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)