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

By: nerd

nerd — Tue, 31 May 2011 16:39:50 +0000

you right, but i think that return just a value there is a bad practice or bad use of JSON cause if we are talking about JSON (JavaScript Object Notation) responses, return a lonely value is the mistake (even if in javascript everything is an object).

You right, but if programmers do not understand what JSON it is then we should correct to teach the right way.

Regards!

By: Dave Ward

Dave Ward — Tue, 31 May 2011 16:23:52 +0000

People often return scalar values from their methods (which is valid JSON with the .d wrapper). A boolean indicating success/failure of an update is common, for example. If that method returns false, the ternary approach would pass
{ d: false } back through the dataFilter instead of false. Same issue with any methods that might return 0 or an empty string. If you're never returning anything but an object, the ternary should be safe, yes.

By: nerd

nerd — Tue, 31 May 2011 16:17:25 +0000

but if you return valid json structures there is no way that the value could be an unexpected ‘false’ or ‘null’, actually i use this code in almost 6 applications in different servers and different .Net frameworks and i don’t get any error, when you return a json object you know the sctructure and possible values, so you shouldn’t get any surprise.

By: Dave Ward

Dave Ward — Tue, 31 May 2011 16:09:39 +0000

You would run into trouble there if the return value was intentionally the value false or something ambiguously falsy like the number 0 or null.

By: nerd

nerd — Tue, 31 May 2011 16:07:03 +0000

actually, can be converted to:

data = data.d ? data.d : data;

By: A quick guide to have jQuery call your ASP.NET PageMethods « I Came, I Learned, I Blogged

Sat, 21 May 2011 15:15:58 +0000

[...] be the case, although a more complex solution for checking if a ‘d’ is there already exists. Anyway, the proposed solution simply takes a JSON string returned from from the server, parses it [...]

By: ASP.NET, AJAX i JSON « Asp.net « Web Development « Pure Development Blog

Sun, 08 May 2011 00:09:27 +0000

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

By: Robin Herbots

Robin Herbots — Mon, 18 Apr 2011 11:27:29 +0000

As from Jquery 1.5 I use the following to solve the .d

converters: {
// Evaluate text as a json expression
“text json”: function(data) {
var dataObj = $.parseJSON(data);
return dataObj.hasOwnProperty(‘d’) ? dataObj.d : dataObj;
}
}

By: Jordan

Jordan — Mon, 28 Mar 2011 23:08:05 +0000

THANK YOU.

I was about to blow my brains out because of this stupid design choice.

By: Mikke!!!

Mikke!!! — Sat, 29 Jan 2011 20:16:09 +0000

Daaaamn this was my fk problem all the day, saved to kill my self :( hahaha
just note:
i dunno why the response, filtering the d isn’t reco by JS, is you debug thru the response is a JSON….

By: Dave Ward

Dave Ward — Mon, 12 Jul 2010 13:47:14 +0000

The first thing I would do in that situation is to watch the response in Firebug to see what’s coming back. If it’s not hitting your success handler at all, you might be throwing a 500 error on the server-side.

Also, double check that there are no JavaScript errors on the page.

Finally, if you’re triggering the $.ajax() call with an element that also triggers page navigation or form submission, be sure that you’re using return false or event.preventDefault to prevent that from occurring. Otherwise, the browser will usually navigate before the $.ajax() callback completes, making it seem like the $.ajax() call didn’t work. This can be especially confusing with form submissions, since they may very quickly refresh the page and it isn’t obvious that anything happened.

By: Doug McDonald

Doug McDonald — Thu, 08 Jul 2010 13:29:02 +0000

I seem to be hitting a very similar issue with returning msg.d.

It’s presumably either returning but not getting into the ‘success’ block or just not returning at all.

Any ideas on a way round this?

By: Fergal Breen

Fergal Breen — Wed, 23 Jun 2010 15:16:50 +0000

It simply did not return at all :S
FYI: Net 3.51

By: Dave Ward

Dave Ward — Wed, 23 Jun 2010 15:13:23 +0000

That should only work on the .NET 2.0 version that doesn’t include the .d. What trouble did you have with returning msg.d?

By: Fergal Breen

Fergal Breen — Tue, 22 Jun 2010 11:10:24 +0000

I had trouble with:

if (msg.hasOwnProperty(“d”))
return msg.d
else
return msg;

I converted to:
if (msg.hasOwnProperty(“d”))
return msg.valueOf;
else
return msg;

Any thoughts on this tactic?