ObjectList Rendering Problems in Windows Mobile 5 Versions


    Sponsored Links


  • 1. 400 bad request with xhtml
    Hello, I have a strange problem. I have a page (igolf.gvn.nl/b) which works fine on a mobile device without xhtml (e.g. chtml device). When I load the page from an (xhtml) Siemens S55 (or any other Siemens) device the page still loads fine, but when clicking on a link (href) a "400 bad request" error occurs. The real strange thing is that these pages are just simple (x-)html, so no strange scripting in asp or aspx. When I upload these same html pages to a Unix (Linux) server and request the exact same pages from the Siemens S55 the link works fine and I get no 400 bad request. This indicates to my opinion that the html itself is not the problem, nor is the Siemens. It looks like the configuration of the server is the problem, but why and how. The web.config cannot be the reason of the problem as this is not used by html pages, it should use the old asp dlls. Does anyone have a idea. Please help as this is a very frustrating issue and I need to solve it quickly. Regards Stefan
  • 2. Windows Integrated Security and wireless
    I have written an ASP.Net application that is to be accessed via a slow wireless network ( < 10kbps ). The web pages do not use viewstate, which keeps my pages around 8K. What I have found when using Windows Integrated Security (WIS) is that it seems to post once, fail, then post again successfully. This kills the performance of the wireless connection. My pages consist of a couple of layers of user controls that contain user controls but it appears that these process within microseconds on the server, so I don't think this is a problem. Is this the way WIS works with ASP.net? Thanks. STom

ObjectList Rendering Problems in Windows Mobile 5 Versions

Postby andrew.cripps » Fri, 13 Oct 2006 21:03:43 GMT


We're using an ObjectList control to produce a neat table of data for
rendering on Windows Mobile 5 devices through IE.

We've got two different Windows Mobile 5 devices - device A is OS
5.1.70 Build 14409.1.1.2, device B is OS 5.1.195 Build 14955.2.3.0
(i.e. device B is a later ROM).

On the older build, the rendering works fine. On the later build, it
ignores the fact that it should be a table and just outputs a bare
horrible-looking list.

I can't find anything on this anywhere, has anyone experienced a
similar problem? 

Any help greatly appreciated.



Re: ObjectList Rendering Problems in Windows Mobile 5 Versions

Postby andrew.cripps » Thu, 19 Oct 2006 15:26:02 GMT

I've answered my own question!

The device that was faulty had an HTTP_USER_AGENT which did not start
with Mozilla/4.0, instead had
Vodafone/1.0/HTC_Mercury/, which meant that the
browser capabilities failed.

In my case I hacked the registry of the device to remove all the
Vodafone cr@p and rendering worked fine. You could also handle this
server-side I guess.

Similar Threads:

1.Differences between Windows Mobile 5 and Windows mobile 6 versions

Hello All,

Can I know what are the differences between Windows Mobile 5 and Windows 
mobile 6 versions in terms of new API support.

Is there a backward compatibility from WM 6 to WM5?

Please answer my query.
Thanks in advance.


2.ASP.NET Mobile problem on Windows Mobile 2003 IE devices

Ie written a simple application that uses the 
System.Web.UI.MobileControls.List control.

The ItemCommand event redirects to other mobile using RedirectToMobilePage.

This works fine in IE6 and low level WAP mobiles however the link doesn 
work on Windows Mobile 2003 IE?

Has anyone else seen this problem?

Many thanks

3.ObjectList list view shows empty data when postback and rendering using item template

4.Problem with mobile:link rendering on Nokia devices

5.Windows Mobile 2003 class libraries versus Windows Mobile 5 class libraries

Im working on some .NET CF 2.0 class libraries that will be used both in 
Windows Mobile 2003 an Windows Mobile 5 applications.
I create them as Windows Mobile 2003 class libraries. Are there any issues 
with this? Or are there any differences between a class library created as
Windows Mobile 2003 class library and a Windows Mobile 5 library?

Thore Berntsen. 

6. Windows Mobile 6 SDK Refresh for Windows Mobile 5

7. Convert Windows Mobile 2003 project to Windows Mobile 5

8. Pocket Access : is it available in Windows Mobile 2003 and Windows Mobile 2003 SE

Return to ASP.NET


Who is online

Users browsing this forum: No registered users and 6 guest