Why XAML Is Important

XAML was first announced publicly at the October 2003 Microsoft Professional Developers Conference (PDC) in Los Angeles as "Longhorn's X Technology." It is a declarative programming model based on a new XML vocabulary called Extensible Application Markup, code-named 'XAML' (pronounced 'zammel').

Writing an application starts with authoring a XAML file (typically through a designer) to define the layout of UI elements which can then be deployed either as a Windows Client UI or a Web UI.

But XAML's potential extends beyond graphical UI development. It is, in fact, a mechanism for instantiating .NET classes. Note that XAML is also a key technology element of the new Windows Workflow Foundation (WWF) and has many other potential uses as well. XAML is an extremely broad and versatile way to put a declarative front-end on .NET development of any sort whatsoever.

Just as there's nothing about object-oriented development that limits it to GUI objects, there's nothing about XAML that limits it to providing a declarative means of creating a richer GUI experience for users.

XAML is analogous to Language Integrated Query (LINQ) in that both are ways to evolve from a more domain-specific procedural approach of program development to a more declarative way of programming. XAML provides an adaptable declarative framework that can potentially be used in all sorts of specific application domains. It offers extensible means to build declarative front-ends over object-oriented programming, which is typically still quite procedural.

Check it out!