Last post Dec 20, 2007 09:22 AM by jpitt57488
Dec 19, 2007 02:05 PM|jpitt57488|LINK
I am writing an application that will be used on a Windows Mobile 5.0 device (only). I have been using Windows Mobile forms and I am able to do what I need to do; however I find that there are many limitations of the mobile forms and controls. For example,
you can't have a SelectionList that posts back automatically. Another good example is you cannot have a multi-line textbox without writing a custom control.
I have played around with writing some regular ASP.net forms and viewed them in the browser in the emulator. They look fine, however some of the behavior is not the same (such as postbacks). I believe this is because some of the built-in client-side java
script is being removed.
I have found that many things that I need to do are only possible when using the DeviceSpecific control. For example, It is a requirement that the textbox posts back automatically as the input is coming from a barcode scanner. I was only able to make this
to run on a WM 5.0 browser in a regular (non-mobile) ASP.net form?
Dec 19, 2007 05:50 PM|pnv.ravikiran|LINK
Hi as per my knowledge people generally used asp.net mobile web pages to build wap sites. Wap sites will be browsed in wap enabled phones.
That doesn’t mean that asp.net mobile web pages doesn’t run on WM 5.0, but as you said a site developed using asp.net mobile web pages will have a great limitations.
For further information please refer to the following url
Please mark as “Answer” if you find this post helpful
Dec 19, 2007 11:44 PM|sundaram.k|LINK
In Wm 5.0 u can use standard ASP.Net control also but by use device specific controls
u can use all asp.net controls inside device specific controls.
In WM 5.0 support java script also,suppose if u want post back control u can use standard asp.net controls inside the device specific controls.......
Dec 20, 2007 09:12 AM|jpitt57488|LINK
Thank you for the response. I ran some quick tests and it looks like ClientScript.RegisterClientScriptBlock does work on on a regular asp.net page from WM.
I think for my purposes I may be better off writing regular ASP.net pages and just laying out the controls so that they are suited for the WM device.
Dec 20, 2007 09:22 AM|jpitt57488|LINK
Thank you for your response. You are correct, I have found that I can use any control inside a template within a Device Specific control. Another trick I learned was that you can wrap a control (or controls) in a User Control. If you put standard asp.net
controls inside a Mobile User Control you will see errors when you view the source aspx, however it will build and seems to work OK.
Placing the controls inside a Device Specific template is probably a cleaner way to go if you want to use standard ASP.net controls within a mobile web form.
As I mentioned in the previous post, I think I am going to consider writing standard ASP.net pages and laying out the controls. It just saves me the trouble of having to place many controls inside a DeviceSpecific control or a user control. I know I will
miss some of the mobile controls, such as the form and the objectlist.
I just thought I would mention that I found that implementing the same functionality in a standard ASP page made a significantly larger page, thus it took a significantly longer time to load the page. I opted to implement in Mobile Web Forms and wrestled
with the DeviceSpecific control to add functionality (such as focus and post-back).