Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 10, 2009 05:44 PM by smanchir2
Apr 09, 2009 08:20 AM|LINK
We have an asp.net 2.0 web application that works fine in Windows Mobile 5 (using mobile IE).
We're trying to get it to work with a new Windows Mobile 6 device (Samsung Epix) and running into a lot of problems. The first issue was that linkbuttons stoppped working entirely. This was solved, or at least work-around, by setting the ClientTarget to
"ie5" or "uplevel".
the rfv out (or even change to another validation group) and the control works, add the rfv and the control fails. We're not using any form of custom validation, just 'plain vanilla' required fields.
Now, we could rewrite the application without using the validators, but that would be a lot of work, and I can't help but wonder if there's something else I'm missing here; these are two very 'simple' .Net elements, linkbuttons and rfvs, and neither of them
mobile ie .browser files to no avail.
mobile .net web ie
Apr 10, 2009 06:16 AM|LINK
I think you will not get the answer in this forum because such information is only sold by consulting firms and professional developers.
Apr 10, 2009 05:44 PM|LINK
I'm not sure I follow, I don't need information on how to redevelop the application; we're certainly able to do that if needed. The problem is that two very basic asp .net controls seem to be nonfunctional in the implementation of IE on this device, which