It's not that it's wrong. It's just Microsoft's format. JSON date encoding is not a trivial topic. See this thread: http://groups.google.com/group/castle-project-users/browse_thread/thread/e63380630223c706
On Jul 16, 10:43 am, Wayne Douglas <[email protected]> wrote: > Hey > > calling NewtonsoftJSONSerializer().Serialize(collection) where there's > dates involved - yields horrid results. > > I know that if I were using the Newtonsoft.Json direct I would be able > to pass in a Newtonsoft.Json.Converters.JavaScriptDateTimeConverter > > but NewtonsoftJSONSerializer().Serialize doesn't like that - is there > anything in the stack that can handle this or do I need to write my > own? > > -- > Cheers, > > w:// --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
