You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to this issue: DateTimeOffsets get converted to local time when deserialized I am wondering if this type of functionality takes place in the v3 version? What I mean? Right now, I am unable to write that kind of code by using v3: DocumentClient = new DocumentClient(new Uri(uri), primaryKey, new JsonSerializerSettings() { DateTimeZoneHandling = DateTimeZoneHandling.Utc }, connectionPolicy: new ConnectionPolicy { ConnectionMode = ConnectionMode.Direct, // ConnectionMode.Gateway is the default ConnectionProtocol = Protocol.Tcp })
And if this still happens in the v3 how can I resolve that issue? Or maybe right now in the v3 this is default behavior that date is serialized in UTC?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello there,
According to this issue: DateTimeOffsets get converted to local time when deserialized I am wondering if this type of functionality takes place in the v3 version? What I mean? Right now, I am unable to write that kind of code by using v3:
DocumentClient = new DocumentClient(new Uri(uri), primaryKey, new JsonSerializerSettings() { DateTimeZoneHandling = DateTimeZoneHandling.Utc }, connectionPolicy: new ConnectionPolicy { ConnectionMode = ConnectionMode.Direct, // ConnectionMode.Gateway is the default ConnectionProtocol = Protocol.Tcp })
And if this still happens in the v3 how can I resolve that issue? Or maybe right now in the v3 this is default behavior that date is serialized in UTC?
Beta Was this translation helpful? Give feedback.
All reactions