I was writing a website that tracked and displayed timestamps, and I only cared about what the time was on the client's machine. The server or database time was irrelevant. This seemed easy, just generate the timestamps on the client and I was all set, right? Wrong!
Server: Web API
I'm using ASP.NET Web API RC (which comes with MVC 4). I found that when the timestamps were passed into my actions, the UTC date had been helpfully converted into a DateTime which was in my server's local time. Gee, thanks... Note to self, call ToUniversalTime() on my incoming DateTime objects. I also made sure that I was never using DateTime.Now and instead used DateTime.UtcNow if I needed to generate a timestamp on the server.
Database: Entity Framework
So I was saving my UTC DateTime values in SQL Server successfully but when reading the values out (using Entity Framework code first), the DateTime's were no longer UTC and instead were coming out with a DateTimeKind of Unspecified, which when serialized to JSON and sent back to the client is treated as a local time. To fix this, you can simply call DateTime.SpecifyKind(timestamp, DateTimeKind.Utc) for any timestamps read from the database.
Since my model had timestamps everywhere, I simplified things by forcing all my timestamps to be read from and written to the database as UTC in a single location. To do this I modified my DbContext to identify any DateTime properties on the model and set the DateTime to UTC if the DateTimeKind is Local or Unspecified.
Here's a generic converter that I'm using in my DbContext to handle the UTC conversions. It can identify a DateTime? or DateTime property on your model, caches the reflected type information and automatically converts all DateTime properties to UTC.
I am makings use of 2 extension methods on the Object type, Get and Set which allows me to dynamically get and set values on my model.