How to begin Mobile Web Development using ASP.NET
Friday, October 23rd, 2009
Keidrick Pettaway asked:
Throughout the course of history of Web Development all information and content has went from static, to sites producing content “on demand” or dynamic if you will.
The object of this model was to deliver the information to Personal Computers, or MAC’s but it was never really designed for use on Mobile devices.
In comes the PDA. Those same sites don’t display properly on a PDA or cell phone.
Due to the fact that is uses a mini-browser and generally supports non-HTML markup.
In addition to not truly supporting HTML these devices have smaller CPUs, smaller I/O devices, and a nominal battery life at best.
All things considered for developers it is still imperative to build apps for these devices.
While building these apps they need to be simple, buy yet efficient due to the parameters that you are working with on a Mobile device.
To begin building a Mobile App using ASP.Net, you will need to use the System.Web.Mobile Namespace which is included in the .NET Framework.
The Namespace comes loaded with ASP.NET Mobile Controls, as well as authentication for your Mobile apps.
ASP.NET Mobile Namespace(s) Namespace Description System.Web.Mobile Includes core mobile functionality System.Web.UI.MobileControls.Adapters Includes Core adapter classes System.Web.UI.MobileControls Includes ASP.NET Mobile Controls
With the combination of these namespace you now have the building blocks, or as my friend Joe calls them “Legos” to be begin building a Mobile Application.
Once a request is made from the server to retrieve a page the System.Web.Mobile Namespace takes a look at the HTTP headers to determine the device type and the browser being used.
At this point the server produces the proper control from the System.Web.UI.MobileControls Namespace, and it also selects the coinciding adapter from System.Web.UI.MobileControls.Adapters based on the device type.
Compendium:
In this article I have given you the foundation to being using Mobile Controls.
Happy Coding
Throughout the course of history of Web Development all information and content has went from static, to sites producing content “on demand” or dynamic if you will.
The object of this model was to deliver the information to Personal Computers, or MAC’s but it was never really designed for use on Mobile devices.
In comes the PDA. Those same sites don’t display properly on a PDA or cell phone.
Due to the fact that is uses a mini-browser and generally supports non-HTML markup.
In addition to not truly supporting HTML these devices have smaller CPUs, smaller I/O devices, and a nominal battery life at best.
All things considered for developers it is still imperative to build apps for these devices.
While building these apps they need to be simple, buy yet efficient due to the parameters that you are working with on a Mobile device.
To begin building a Mobile App using ASP.Net, you will need to use the System.Web.Mobile Namespace which is included in the .NET Framework.
The Namespace comes loaded with ASP.NET Mobile Controls, as well as authentication for your Mobile apps.
ASP.NET Mobile Namespace(s) Namespace Description System.Web.Mobile Includes core mobile functionality System.Web.UI.MobileControls.Adapters Includes Core adapter classes System.Web.UI.MobileControls Includes ASP.NET Mobile Controls
With the combination of these namespace you now have the building blocks, or as my friend Joe calls them “Legos” to be begin building a Mobile Application.
Once a request is made from the server to retrieve a page the System.Web.Mobile Namespace takes a look at the HTTP headers to determine the device type and the browser being used.
At this point the server produces the proper control from the System.Web.UI.MobileControls Namespace, and it also selects the coinciding adapter from System.Web.UI.MobileControls.Adapters based on the device type.
Compendium:
In this article I have given you the foundation to being using Mobile Controls.
Happy Coding