How to pass a JSON date value via ASP.NET MVC using JSON.NET?

Question

Possible Duplicate:
Format a Microsoft JSON date?

The ASP.NET function Json() formats and returns a date as

{"d":"\/Date(1240718400000)\/"}

which has to be dealt with on the client side which is problematic. What are your suggestions for approaches to sending date values back and forth?

Solution 1

This was found in another post on Stack Overflow:

var date = new Date(parseInt(jsonDate.substr(6))); 

The substr function takes out the "/Date(" part, and the parseInt function gets the integer and ignores the ")/" at the end. The resulting number is passed into the Date constructor.

Solution 2

If you are not tied to the MS JSON serializer you could use Json.NET. It comes with an IsoDateTimeConverter to handle issues with serializing dates. This will serialize dates into an ISO 8601 formatted string.

For instance, in our project serializing myObject is handled via the following code.

JsonNetResult jsonNetResult = new JsonNetResult();
jsonNetResult.Formatting = Formatting.Indented;
jsonNetResult.SerializerSettings.Converters.Add(new IsoDateTimeConverter());
jsonNetResult.Data = myObject;

If you decide to take the Json.NET plunge you'll also want to grab JsonNetResult as it returns an ActionResult that can be used in ASP.NET MVC application. It's quite easy to use.

For more info see: Good (Date)Times with Json.NET

Solution 3

It may be ugly, but it works:

 var epoch = (new RegExp('/Date\\((-?[0-9]+)\\)/')).exec(d);
 $("#field").text((new Date(parseInt(epoch[1]))).toDateString());

Probably, it is not necessary to match the whole string, and just (-?[0-9]+) is enough...

Solution 4

Not everyone agrees with me that it's a good idea, but I find myself most often returning formatted strings instead of proper dates. See How I handle JSON dates returned by ASP.NET AJAX.

Solution 5

After playing with the Json.NET library, I'm wondering why you would choose to use the IsoDateTimeConverter over the JavascriptDateTimeConverter.

I found this to be easier to use with the Ext JS interfaces that I was using when serializing dates from an MVC Controller.

JsonNetResult jsonNetResult = new JsonNetResult();
jsonNetResult.Formatting = Formatting.Indented;
jsonNetResult.SerializerSettings.Converters.Add(new JavaScriptDateTimeConverter());
jsonNetResult.Data = myObject; 

I'm getting this data back into an Ext.data.JsonStore which is able to get the returned value as a date without me having to specify a date format to parse with.

        store:new Ext.data.JsonStore({
            url: pathContext + '/Subject.mvc/Notices',
            baseParams: { subjectId: this.subjectId },
            fields: [
               {name: 'Title'},
               {name: 'DateCreated', type: 'date' }
            ]
        }),

The JSON returned looks like this:

[{"Title":"Some title","DateCreated":new Date(1259175818323)}]

There isn't any reason to convert to ISO 8601 format and back if you don't have to.

View more solutions

Comments

[ChrisP]

This provides some insights, but deals w/ jQuery to ASP.NET web service rather than an MVC controller returning JsonResult via Json(). I am interested in jQuery to ASP.NET MVC w/o MSFT ajax.

[Alex]

The JSON format is the exact same in the example to what you described. Date Property or Single Date Value does not make a difference.

[Marc]

Don't know how we missed this, thanks

[DalSoft]

Simplest solution is the best

[Brian Rogers]

Because the JavaScriptDateTimeConverter does not produce valid JSON. If you want to maintain interoperability with a wider range of clients that expect valid JSON, then you'd be better off sticking with ISO 8601.