TimeZone Serialization Issue

[mrellipse]

The custom MVC input/output formatters are incorrectly implemented.

They modify a shared/global version of Json SerializerSettings (through a class instance). This is not a thread-safe approach. Also, it is appending rather then upserting the DateTime converter.

So a side-effect of this is that the very first converter instance added to Serializer Settings is determined by localization cookie of the first user to hit the website after bootstrapping.

[mrellipse]

fixed the issue by creating customer serializer settings, and writing output directly to HttpResponse screen.

also simplified date/time conversion helpers

behaviour is now consistent

[mrellipse]

merged