Comments on: Never worry about ASP.NET AJAX’s .d again

By: Chris Haines

Chris Haines — Thu, 21 Jan 2010 17:13:17 +0000

Ah! Wish I’d found that post 2 hours ago… :)

By: Dave Ward

Dave Ward — Thu, 21 Jan 2010 17:01:10 +0000

I haven’t had a chance to experiment with it yet myself, but I think Adam is on the right track here: http://encosia.com/2009/07/21/simplify-calling-asp-net-ajax-services-from-jquery/#comment-37801

By: Chris Haines

Chris Haines — Thu, 21 Jan 2010 16:08:55 +0000

I think this fails now in Jquery 1.4 – just doing some testing, and think it fails if your server is returning a simple type, e.g. a string….

Seems that jquery 1.4 doesn’t accept non-valid JSON now, and in returning msg.d from the data filter, jquery then rejects it.

any ideas?

By: Dave Ward

Dave Ward — Sat, 28 Nov 2009 17:48:52 +0000

I don't think the try/catch does anything there, does it? msg.hasOwnProperty is safe to call, even if msg has no properties. In the end, you're better served by using dataFilter and doing this processing before the success handler. That way you can both improve the JSON parsing and not have to repeat the ".d" checking for every $.ajax call you make.

By: Desmati

Desmati — Sat, 28 Nov 2009 14:28:09 +0000

There is a very simple way:

success: function(msg) {
try {
if (msg.hasOwnProperty(“d”))
msg = msg.d;
}catch(ex){}
DoSomthing();
}

By: Creating a Webservice Proxy with jQuery « Life of a geek and a part-time poet

Tue, 11 Aug 2009 10:00:15 +0000

[...] Never worry about ASP.NET AJAX’s .d again [...]

By: Satheesh

Satheesh — Wed, 29 Jul 2009 03:21:24 +0000

Excellent post!! Thanks!

By: Justin Kohnen

Justin Kohnen — Mon, 13 Jul 2009 15:06:13 +0000

Great post, thanks for all your hard work, and code samples.

By: Weekly Web Nuggets #70 : Code Monkey Labs

Weekly Web Nuggets #70 : Code Monkey Labs — Mon, 06 Jul 2009 03:03:13 +0000

[...] Never Worry About ASP.NET AJAX’s .d Again: Dave Ward shows an elegant way to call ASP.NET AJAX JSON services with jQuery. In other news, jQuery totally rocks! [...]

By: deef

deef — Thu, 02 Jul 2009 09:16:17 +0000

Thanks so much for this post and all your other posts. I’m looking forward to a follow-up post on this matter once jQuery 1.3.3 is released. Keep up the good work.

By: Arjan’s World » LINKBLOG for June 30, 2009

Arjan’s World » LINKBLOG for June 30, 2009 — Tue, 30 Jun 2009 20:04:04 +0000

[...] Never worry about ASP.NET AJAX’s .d again – Dave Ward What’s that .d yu ask? ‘ By encapsulating the JSON response within a parent object, the framework helps protect against a particularly nasty XSS vulnerability ‘ [...]

By: DotNetBurner - ASP.net Ajax

DotNetBurner - ASP.net Ajax — Tue, 30 Jun 2009 11:34:52 +0000

Never worry about ASP.NET AJAX’s .d again | Encosia…

DotNetBurner – burning hot .net content…

By: Reflective Perspective - Chris Alcock » The Morning Brew #379

Reflective Perspective - Chris Alcock » The Morning Brew #379 — Tue, 30 Jun 2009 07:57:28 +0000

[...] Never worry about ASP.NET AJAX’;s .d again – Dave Ward looks at insulating yourself and your code from the problems with JSON from different versions of the ASP.NET framework [...]

By: Krishna Chaitanya

Krishna Chaitanya — Tue, 30 Jun 2009 05:45:27 +0000

Hi Dave,
I wonder how you know people’s pulse! Whenever I get stuck at some problem, you come up with a solution for the same problem as if I asked you :)

It was very incidental that I got stuck with same problem now as I am using jqGrid plugin (which you suggested in mail). I’ve blogged about it here.
Thank you for the article:)

By: Dave Ward

Dave Ward — Tue, 30 Jun 2009 04:02:20 +0000

It’ll change in jQuery 1.3.3, to about the same as what I’m showing in my next post (using browser native JSON.parse if available). At that point (my next post), doing it in the dataFilter will be better than what jQuery’s doing, not just copying it.

Either way, you don’t have much choice if you want to transform the data independent of the success handler. Running a transform in the dataFilter via $.ajaxSetup is a must when working with some jQuery plugins that don’t otherwise play nice with “ScriptServices” and page methods.