Buliding A WAP Site

Description

WAP stands for Wireless Application Protocol. The Wireless Application Protocol (WAP) provides a universal open standard for bringing Internet content and advanced services to mobile phones and other wireless devices.

Requirements for development

To develop mobile applications with .NET, you must download and install the following components. IE and the .NET SDK can be downloaded from the Microsoft MSDN site for free.

• Windows 2000 Professional/Server/Advanced Server OS 
• Internet Explorer 5.5
• NET framework Beta 1
• NET Mobile Web SDK Beta 1
• Your favorite WAP simulator.

Mobile Forms

Mobile Web Forms Controls that generate markup language for different devices. The Mobile Internet Toolkit consists of a set of server-side mobile Web Forms controls and the Mobile Internet Designer for authoring the user interface.

A mobile Web Forms page is a specialized ASP.NET Web Forms page. It's a text file with the .aspx extension, and it contains mobile controls that can adaptively render to supported mobile devices.

Every mobile Web Forms page must have the following standard header directives, which identify it as a mobile page. The Language attribute will vary, depending on which language is chosen for development.

<%@ Page Inherits="System.Web.UI.MobileControls.MobilePage" Language="C#" %>
<%@ Register TagPrefix="mobile"
Namespace="System.Web.UI.MobileControls"
Assembly="System.Web.Mobile" %>

These directive tell the .NET Framework that this page inherits the Mobile Web Form functionality, and the TagPrefix "Mobile" identifies Mobile Server Controls. Every mobile control tag on a mobile Web Forms page should include the runat="server" attribute:

Every Mobile Web Form must have atleast one form in it (identified by the <Mobile:Form> tag

The ASP .NET common language runtime (CLR) dynamically compiles and creates an instance of a page class that inherits from System.Mobile.UI.MobilePage.

As indicated in the Language attribute, the language is C#. The second line registers "Mobile" as shortcut for "System.Mobile.UI". This is used in control elements to avoid writing <System.Mobile.UI:ControlName>.

The following example shows simple WAP site with Mobile Forms

Source Code:

//Sorce Code Starts
<%@ Import Namespace="System.IO" %>
<%@ Page Inherits=" System.Web.UI.MobileControls.MobilePage"Language="cs" %>
<%@ Register TagPrefix="mobile"
Namespace="System.Web.UI.MobileControls"
Assembly="System.Web.Mobile" %>
<% @Import Namespace="System.Xml"%>
<script runat="server">
public void List_ClickEventHandler(Object source, ListCommandEventArgs e)
{
String sportstr;
switch (e.ListItem.Value)
{
case "aboutus":
//code here
break;
case "services":
//code here
break;
case "clients":
//code here
break;
case "careers":
//code here
break;
case "contactus":
CompanyLabel.Text = "contact at [email protected]";
break;
case "feedback":
//code here
break;
default:
//code here
break;
}
ActiveForm = Company;
}
</script>
//List of Sports
<mobile:Form runat="server">
<mobile:Label runat="server">T.R.R Technologies</mobile:Label>
<mobile:List runat="server" id="ListProducevalue"OnItemCommand="List_ClickEventHandler" >
<item Text="About us" Value="aboutus" />
<item Text="Services" Value="services" />
<item Text="Clients" Value="clients" />
<item Text="Contact us " Value="contactus" />
<item Text="Careers" Value="careers" />
<item Text="Feedback" Value="feedback" />
</mobile:List>
</mobile:Form>
<mobile:Form id="Company" runat = "server">
<mobile:Label runat="server" id="CompanyLabel"/>
</mobile:Form>
//Source Code End

Architecture of the .NET framework application development.