Maybe. I started playing around with it a while ago to see if it would be
useful or not and so far, I found it quite interesting. Not useful yet but
getting there. I haven't had the chance to look at all of the controls or
extenders yet but making my way there. I have found 1 control that could
prove extremely useful in saving postbacks when changing content on a
website. Its the accordion control. It can change the content of parts of
the site without postbacks. The update pannel is the same way. I have been
tempted to ajax up every possible place possible on my website, but hold
off. Guess I'm sort of conservative on that point (don't do it unless its
required). Part of this is company saying it has to be that way but....if it
were my choice?...
Either way, it looks like a good choice. If you use the accordion control,
watch out because it has a few bugs in it. The problems with it are:
1. In design mode, when adding accordion panes, the designer doesn't put the
<Panestag around the pane controls.
2. You have to remove the accordion_extender control from the accordion
control since it appears that a "accordion_extender" never has existed.
3. It appears that you have to manually insert the SelectedIndex="..."
property since the designer fails to include it in the code.
They are all not that hard to work around though (after trying to figure it
out for a while). So, at this point, not for sure what to think. HTH...
"Wannabe" <Wa*****@discussions.microsoft.comwrote in message
news:E2**********************************@microsof t.com...
We are looking at Ajaxing our existing web application. Question
is...Should
we Ajax any and everything we can, or not? One example...if a page posts
back
to itself, is that a good candidate for Ajax?