In this blog I am trying to explain the concept of XAML.
XAML stands for Extensible Application Markup Language and
it is a declarative markup language. As applied to the .NET Framework
programming model, XAML simplifies creating a UI for a .NET Framework
application. You can create visible UI elements in the declarative XAML markup,
and then separate the UI definition from the run-time logic by using
code-behind files, joined to the markup through partial class definitions. XAML
directly represents the instantiation of objects in a specific set of backing
types defined in assemblies. This is unlike most other markup languages, which
are typically an interpreted language without such a direct tie to a backing
type system. XAML enables a workflow where separate parties can work on the UI
and the logic of an application, using potentially different tools.
When represented as text, XAML files are XML files that
generally have the .xaml extension. The files can be encoded by any XML
encoding, but encoding as UTF-8 is typical.
The following example shows how you might create a button as
part of a UI. This example is just intended to give you a flavor of how XAML
represents common UI programming metaphors (it is not a complete sample).
<Button Content="Click Me!"/>
Properties of an object can often be expressed as attributes
of the object element. An attribute syntax names the property that is being set
in attribute syntax, followed by the assignment operator (=). The value of an
attribute is always specified as a string that is contained within quotation
<Button Background="Red" Foreground="White" Content="Click Me!"/>