Question: > 
> **Possible Duplicate:**  
> 
> [Format a Microsoft JSON date?](https://stackoverflow.com/questions/206384)
> 
> 
> 

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?

Answer: 
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](http://en.wikipedia.org/wiki/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.
Take a look at the blog post *[jQuery, Ajax, ASP.NET and dates](http://schotime.net/blog/index.php/2008/06/19/jquery-ajax-aspnet-and-dates/)*.

It details how to work with ASP.NET MVC and jQuery to pass dates via JSON between the server and client side.