Goodbye Microsoft AJAX Library
Microsoft AJAX Library is no more… for me!
No more Sys.<Whatever>!
I’ve seen the light, I shall jQuery all the way… to scripting heaven!
P.S. I may still use one or two JavaScript extensions (e.g. String.format) from the Microsoft AJAX Library!
What about the DataContext, Dataview, Client templates and Bindings. Surely ASP.NET Ajax 4.0 is better at doing this than jQuery? Please explain your remark in more detail. Cheers.
Chris Bower
April 27, 2009 at 10:37 am
Superb blog! I just discovered it but am going to bookmark it on my tech blog.
Anyhow, I discovered jQuery a few weeks ago after hearing a talk by Rod Paddock out of Austin, TX. I’m very much sold on jQuery and am trying to replace all AJAX Control Toolkit extenders with jQuery equivalents. In fact, I discovered your blog when searching for: jquery validator callout
One roadblock I *seem* to have come up against on my path to get rid of all of the Control Toolkit extenders is replacing the Modal Popup Extender when one or more of the button of the dialog box must call server-side code. Perhaps there’s a simple way around this but so far I haven’t found any. If you ever do, I’d most appreciate it if you left a comment here!
Robert Werner
May 7, 2009 at 4:11 am
I’ve never been a fan of the ToolKit to be honest and used it more of a reference than anything else. I too recently ‘found’ jQuery and started using it in conjunction with the ajax library – for me the power there is the type system, control components (like HTCs in the old world, remember those Ting?) and the tight integration of WCF services.
Owain Cleaver
May 31, 2009 at 8:44 am
I too agree the type system is the strongest point of the Microsoft AJAX Library; it enables component development in a structured, “classical” way.
tzkuei
May 31, 2009 at 12:22 pm