ASP.NET AJAX and Windows Mobile - A New Approach

You Can Take it With You

Syndication

News

  • Don't miss the next Windows Mobile Webcast... Unit Testing for Mobile Devices: http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032382824&EventCategory=4&culture=en-US&CountryCode=US.

After spending another couple of hours kicking around inside of the ASP.NET AJAX (Atlas) client-side script files, I've come to a conclusion...

Getting the script files to support Windows Mobile requires some distinct and special code paths separate from the existing generic code. I had really hoped that I could tweak the existing code paths with just some special case conditions but the differences are just too significant. So that'll be where I'll pick up with things tomorrow.

My goal is to get to a place where an UpdatePanel will work. Once I get there, I'll decide how much more effort it'll take to go any further.

Calling it a day (for now)...


Posted Sep 20 2007, 04:12 PM by jim-wilson

Comments

eponymous wrote re: ASP.NET AJAX and Windows Mobile - A New Approach
on 09-20-2007 5:46 PM
Jim,
I've read your posts as you struggle mightily with this task. I admire your efforts, and as I watch you struggle I wonder to myself if there could be a better way?

The philosophy behind building an AJAX web application, as I understand it, is to create a web page that more closely resembles an actual application. What would the arguments be for trying to extend the web model vs. "simply" (I readily admit I do not know the effort) building an application for the platform that harnesses the web to do the job? You've done a great job thus far, and doubtless you'll walk away with significant knowledge of what the browser supports; I'm curious as to what the difference in efforts would be to actually build something more platform-specific...

Keep up the great work!
ttklf4 wrote re: ASP.NET AJAX and Windows Mobile - A New Approach
on 09-21-2007 7:32 AM
I get the following error with ASP.NET AJAX when IEMobile load the scripts:

Sys.ArgumentException: Value must be a DOM element
Jim Wilson wrote re: ASP.NET AJAX and Windows Mobile - A New Approach
on 09-21-2007 8:06 AM
ttklf4;

That is the basic error that IE Mobile always returns when accessing VS2005 ASP.NET AJAX pages.

It happens because the client-side JavaScript tries to check the nodeName property when wiring up the DOM events and IE Mobile doesn't support the nodeName property.

I talk a little about this issue near the end of this post: http://www.pluralsight.com/blogs/jimw/archive/2007/09/20/48529.aspx

Thanks,
Jim
ttklf4 wrote re: ASP.NET AJAX and Windows Mobile - A New Approach
on 09-21-2007 9:00 AM
Thank you very much for this hint, Jim.

If I set the ClientTarget attribute of the page directive to "downlevel" not to "ie5" the error diappears but the UpdatePanel does not work anyway.
Jim Wilson wrote re: ASP.NET AJAX and Windows Mobile - A New Approach
on 09-21-2007 9:13 AM
ttklf4;

You're going to want to read my blog posts for the past few days.

The bottom line is that ASP.NET AJAX pages don't work with IE Mobile. I've been working on ways to modify the AJAX client-side scripts for several days now to figure out if I can find a way to get it all to work.

For now though, ASP.NET AJAX just doesn't work on Windows Mobile.

-Jim
Jim Wilson wrote re: ASP.NET AJAX and Windows Mobile - A New Approach
on 09-21-2007 9:28 AM
eponymous;

I totally understand your point. If it wasn't for the fact that I'm working on several pieces of content around AJAX and Windows Mobile I don't know if I would've developed the interest I have in getting this all worked out.

I've expanded on some of these thoughts in my latest post. http://www.pluralsight.com/blogs/jimw/archive/2007/09/21/48541.aspx

Thank you for your kind words and support. Please keep the feedback coming.

-Jim

Add a Comment

(required)  
(optional)
(required)  
Remember Me?