Skip to main content

What Is XAML?


XAML or Extensible Application Markup Language (pronounced "zammel") is a XML based language used to create rich GUI’s.

  • XAML specifies the user interface for Silverlight or WPF application.
  • XAML is used declare controls on Silverlight or WPF Page. 
  • In simple terms XAML Page is similar to .Aspx Page in asp.net website. 
  • In .Aspx Page we use Html to form UI, while in XAML we use Xml to form UI
  • It supports both vector and bitmap images 
  • XAML is a new markup language which is used for defining UI elements and its relationships with other UI elements. 
  • XAML is a XML document which defines objects and properties and WPF loads this document in actual memory. 
  • Using XAML, you can create any kind of objects that means graphical or non-graphical. 
  • XAML is a declarative XML-based language by which you can define object and properties in XML 
  • XAML document is loaded by a XAML parser. XAML parser instantiates objects and set their properties. XAML describes objects, properties and there relation in between them. WPF parses the XAML document and instantiates the objects and creates the relation as defined by XAML.
Advantages of XAML
  • XAML code is short and clear to read
  • Separation of designer code and logic
  • Graphical design tools like Expression Blend require XAML as source.
  • The separation of XAML and UI logic allows it to clearly separate the roles of designer and developer.

Comments

Popular posts from this blog

HTTPHandler and HTTPModule in ASP.NET

If you want to implement pre-processing logic before a request hits the IIS resources. For instance you would like to apply security mechanism, URL rewriting, filter something in the request, etc. ASP.NET has provided two types of interception HttpModule and HttpHandler .   The web server examines the file name extension of the requested file, and determines which ISAPI extension should handle the request. Then the request is passed to the appropriate ISAPI extension.  For Example When an .aspx page is requested it is passed to ASP.Net page handler. Then Application domain is created and after that different ASP.Net objects like Httpcontext, HttpRequest, HttpResponse. HTTPModule: -    It's just like a filter. The Modules are called before and after the handler executes . -    HTTP Modules are objects which also participate the pipeline but they work before and after the HTTP Handler does its job, and produce additional serv...

Connected and disconnected architecture in ADO.Net with Example

Connected Architecture of ADO.NET The architecture of ADO.net, in which connection must be opened to access the data retrieved from database is called as connected architecture. Connected architecture was built on the classes connection, command, datareader and transaction.  Connected architecture is when you constantly make trips to the database for any CRUD (Create, Read, Update and Delete) operation you wish to do. This creates more traffic to the database but is normally much faster as you should be doing smaller transactions. Disconnected Architecture in ADO.NET The architecture of ADO.net in which data retrieved from database can be accessed even when connection to database was closed is called as disconnected architecture. Disconnected architecture of ADO.net was built on classes connection, dataadapter, commandbuilder and dataset and dataview. Disconnected architecture is a method of retrieving a r...

What is AutoEventWireup?

The ASP.NET page framework also supports an automatic way to associate page events and methods. If the AutoEventWireup attribute of the Page directive is set to true (or if it is missing, since by default it is true ),  AutoEventWireup is an attribute in Page directive.   AutoEventWireup is a Boolean attribute that indicates whether the ASP.NET pages events are auto-wired.  AutoEventWireup will have a value true or false . By default it is true . <% @ Page Language ="C#" AutoEventWireup ="true" CodeBehind ="Default.aspx.cs" Inherits ="WebApplication2._Default" %> the page framework calls page events automatically, specifically the Page_Init and Page_Load methods. In that case, no explicit Handles clause or delegate is needed. Example 1 With AutoEventWireup ="true" HTML Code <% @ Page Language ="C#" AutoEventWireup ="true" CodeBehind =...