<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body><figure class="quote"><figcaption><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="1" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[1]</anchor-end> <cite xml:lang="en">Stand-Alone JSON Serialization</cite>
(<time>2017-06-01 22:19:46 +09:00</time>)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="https://msdn.microsoft.com/en-us/library/bb412170(v=vs.110).aspx#mt154">https://msdn.microsoft.com/en-us/library/bb412170(v=vs.110).aspx#mt154</anchor-external></figcaption><blockquote><p>DateTime values appear as JSON strings in the form of &quot;/Date(700000+0500)/&quot;, where the first number (700000 in the example provided) is the number of milliseconds in the GMT time zone, regular (non-daylight savings) time since midnight, January 1, 1970. The number may be negative to represent earlier times. The part that consists of &quot;+0500&quot; in the example is optional and indicates that the time is of the Local kind - that is, should be converted to the local time zone on deserialization. If it is absent, the time is deserialized as Utc. The actual number (&quot;0500&quot; in this example) and its sign (+ or -) are ignored.</p><p>When serializing DateTime, Local and Unspecified times are written with an offset, and Utc is written without.</p><p>The ASP.NET AJAX client JavaScript code automatically converts such strings into JavaScript DateTime instances. If there are other strings that have a similar form that are not of type DateTime in .NET, they are converted as well.</p><p>The conversion only takes place if the &quot;/&quot; characters are escaped (that is, the JSON looks like &quot;\/Date(700000+0500)\/&quot;), and for this reason WCF's JSON encoder (enabled by the WebHttpBinding) always escapes the &quot;/&quot; character.</p></blockquote></figure></body></html>