G
Guest
when serializing a datetime value and then subsequently desreializing it it
gets modified if the receiving computer is in a different timezone than the
sender. I know how to use the SpecifyKind to set the type to
utc/local/unspecified but the problem is that we serialize a lot of complex
classes that contain DateTime vars at some deep down level.
Is there a patch the .net CLR or some other method available through a
registry entry or something that I can set the default behaviour so that any
datetime object that is created is done with a Kind of utc?
Long term this needs to be fixed. We shouldn't have transport layer stuff
modifying data created at the application layer.
gets modified if the receiving computer is in a different timezone than the
sender. I know how to use the SpecifyKind to set the type to
utc/local/unspecified but the problem is that we serialize a lot of complex
classes that contain DateTime vars at some deep down level.
Is there a patch the .net CLR or some other method available through a
registry entry or something that I can set the default behaviour so that any
datetime object that is created is done with a Kind of utc?
Long term this needs to be fixed. We shouldn't have transport layer stuff
modifying data created at the application layer.