Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a problem with synchronizing DateTime data. When DateTime data is synced it always uses the servers local timezone. I have been searching and reading about this and only found this official workaround:
http://support.microsoft.com/kb/842545
This workaround was posted back in 2007. Is it really true that Microsoft hasn’t released a fix for this problem? If not, is this workaround the only way to solve the problem?
If you have control over both the client and the server, it is always preferable to work with UTC DateTimes (timezone independant). You should then always persist to database (or file or whatever persisting you use) DateTimes with DateTimeKind UTC:
http://msdn.microsoft.com/en-us/library/system.datetime.kind.aspx
The you can delegate to the client to correctly show the time (given the users timezone).
If you haven’t got control over both client and server, I see no workaround but the workaround given by Microsoft. The point is that UTC times should always be used when potentially facing clients in different time zones.
Regards,
Torgeir