tag:blogger.com,1999:blog-36201586.post6955399448171294944..comments2010-10-28T23:36:11.035+01:00Derek Fowlerhttp://www.blogger.com/profile/09963865123124577525noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-36201586.post-58647417421529836902010-10-28T23:36:11.035+01:002010-10-28T23:36:11.035+01:00Excellent, thanks. I was just working through the same problem with multiple layers. DB layer, DTO layer, JSON layer and loads of conversions going on imbetween. I think I need to change the datalayer to ensure the kind is getting set correctly.Scotthttp://twitter.com/toxaqnoreply@blogger.comtag:blogger.com,1999:blog-36201586.post-8931310327573343482010-10-26T10:44:59.470+01:002010-10-26T10:44:59.470+01:00In answer to the guy who posted a comment with a rather politically sensitive message at the end of it...<br /><br />--<br />what if you pass datetime from client to sql server?<br /><br />Now since .net Datetime has a kind member, so when you pass it to server, will the value be converted to local one before it is passed to and stored at server?<br />--<br /><br />If you pass in a DateTime the Kind is ignored and no timezone offset on the database server itself is applied either. When you try to retrieve the value it will come back as Kind Unspecified regardless of the Kind when it was inserted. As I said in the post it is this you have to watch out for, if you&#39;ve inserted a date from one timezone and are retrieving it in another.Derek Fowlerhttp://www.blogger.com/profile/09963865123124577525noreply@blogger.com