Last post Oct 04, 2010 02:58 PM by mthomlins
Sep 22, 2010 04:44 PM|mthomlins|LINK
Im a little aggravated at this issue because it should be a non issue.
I have a very simple application that fully works on a windows mobile platform for scanning barcodes. The application has a simple table with 2 columns. Column 1 contains labels and column 2 contains textboxes.
However once this page is viewed on the scanner all styling is removed including the table layout I want.
Its as if windows mobile IE ignores all styling or can't interpret it.
Thanks in advance,
Sep 23, 2010 09:28 AM|roopeshreddy|LINK
Can you explain the problem bit clearly. How can you view the page on the scanner?
Sep 29, 2010 10:11 AM|mthomlins|LINK
I have a web app designed to work with a mobile scanner.
The page is nothing more then 4 cells 2x2 table
Viewing the application in IE on the mobile scanner results in a 1x4 (Everything is left justified as if the table does not exist.)
Oct 04, 2010 02:58 PM|mthomlins|LINK
Windows Mobile 6 and Windows Mobile 6.1 provide a substantially improved Internet Explorer Mobile browser than that on earlier versions of Windows Mobile. What you may find surprising is that ASP.NET sites that work perfectly with Windows Mobile 5.0 devices
sometimes seem to not work as well with Windows Mobile 6 and Windows Mobile 6.1 devices, which is not what one expects from an "improved" browser.
The problem stems from the fact that ASP.NET sites created with Visual Studio 2008 and earlier do not fully recognize Internet Explorer Mobile on Windows Mobile 6 and Windows Mobile 6.1 devices. Because ASP.NET doesn't recognize Internet Explorer Mobile
on these devices, the capability properties that ASP.NET stores in the HTTP request's
HttpBrowserCapabilities instance are not set correctly. With the capability properties incorrectly set, the Internet Explorer Mobile browser on Windows Mobile 6 and Windows Mobile 6.1 appears to ASP.NET to have extremely limited feature support. The
biggest impact of this being the case is that ASP.NET renders the page content as if the Internet Explorer Mobile browser has no client-side scripting capability. As you probably know, client-side scripting is key to ASP.NET rendering rich and responsive content.
This paper provides an explanation of the changes in Internet Explorer Mobile on Windows Mobile 6 and Windows Mobile 6.1 that create this situation and provides an easy-to-implement solution that will have your ASP.NET sites properly recognizing Internet
Explorer Mobile on Windows Mobile 6 and Windows Mobile 6.1 devices. With these simple changes, ASP.NET content will work as well or better on Windows Mobile 6 and Windows Mobile 6.1 than on earlier versions of Windows Mobile.