ArcGIS Web ADF 9.3 – Is it Any Better?

June 13, 2009

tags:
3 comments

A while back I’ve posted my opinion about the ArcGIS Web ADF 9.2. It wasn’t a positive one. Since then, I’ve had a chance to work a little with the new version – the ADF 9.3, and even attended a seminar held by Rex Hansen, which – as I understood – is one of the main contributors to the design of the Web ADF.

On the surface it seems that the Web ADF took a leap forward at 9.3. It is now built upon the Microsoft Ajax library, instead of ESRI’s own callback-based solution (you know, the whole ICallbackEventHandler headache). Performance should be better, as the map now uses a custom .ashx handler to serve the images, instead of doing a bunch of full postbacks. But the question that remains is – Is the API any better? Are simple stuff simple? Is customization any easier?

Sadly, the answer to that seems to be a big NO. Almost none of the issues I addressed in my original post were fixed. The API is still overly complex. Resources, functionalities and all these so-called abstractions remain in place, emphasizing the strength of the JavaScript API’s simplicity. And yes, there are still about a billion classes that are named “Converter” in the API. It seems like ESRI insists that you write the entire namespace before every class you use.

Ajax is a bit easier this time around, since we can use ScriptManager to register client scripts, but it still took us a while to figure out how to make it all play nicely together (this article provides some solutions, by the way). I hate having to read mountains of documentation before I can get anything done (on the bright side – at least there is documentation), and trying to explain a newbie programmer about the difference between a “partial postback” and a callback is hard.

There are some more unpleasant surprises for you here. Noam Sheffer (hebrew link) mailed me about a problem he had. It seems that the map control still initiates a full postback to the page with every zoom operation.  This is of course bad for performance, and also caused him issues with maintaining the state of some of his controls. Checking out an example site with Fiddler or Firebug, can show you that this is indeed the case.

And a word about the seminar by Rex Hansen. He showed some of the product’s new features, performance tips, and solutions to common problems. Thing is, I don’t care about being able to customize the MapTips template. It shows that ESRI focus is on the wrong thing – instead of simplifying the API, they’re adding more features so that it is even more complex.

Therefore, I still recommend anyone with a choice to go for one of the REST APIs. I’ve only worked with the JavaScript APIs, but I hear that Silverlight and Flex are similar and are equally simple. For now, I’m keeping my strong belief that doing anything complex with the Web ADF is putting yourself in a world of hurt.

Add comment
facebook linkedin twitter email

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

3 comments

  1. Faridur Rahman ChoudhurySeptember 16, 2009 ב 15:08

    Is it possible to have a full-screen map using AGS 9.3 Web ADF? I mean, a map which fits to the screen in different screen sizes like you can with OpenLayers or the AGS Javascript API.

    Reply
  2. JAFebruary 10, 2010 ב 19:49

    Strongly agree. Only pulling my hair out with the web adf to leverage existing .net skills, utilize editing capacity, and make some moderately complex db connections. But, since nothing seems to work out side of ESRI demo environments, I’m ready to try the flex api. Thanks for ths blog, btw!

    Reply
  3. DavidMarch 4, 2010 ב 17:20

    I have Arc infor 9.3 installed with vs 2008 does anyone know where i can get the web adf extension for my vs 2008?

    Reply