http://www.primedigit.com/2008/12/02/sql-server-datetime-conversion/ Thoughts on ASP.NET, Visual Design, SQL Server 2005, C# and much more... Sat, 11 Jun 2011 20:01:33 +0000 hourly 1 http://wordpress.org/?v=3.3 http://www.primedigit.com/2008/12/02/sql-server-datetime-conversion/comment-page-1/#comment-576 Stefan Stenegger Wed, 03 Dec 2008 12:53:30 +0000 http://www.primedigit.com/2008/12/02/sql-server-datetime-conversion/#comment-576 We wrote our own class, because we are additionally storing the offset to UTC with every date and time. The own class checks the range and rounds the ticks in the constructor, and therefore it only holds persistable values and does not change after saving and loading it. And it could be null. We create it using Now or a regular DateTime in the constructor, and get DateTime values again with members like UtcTime or ToLocalTime() and more. No fancy stuff actually. We map it using a component every time (there are two properties to map). This could probably be easier with some NH feature (custom type?), but I didn't have the time to care about this until now. We wrote our own class, because we are additionally storing the offset to UTC with every date and time. The own class checks the range and rounds the ticks in the constructor, and therefore it only holds persistable values and does not change after saving and loading it. And it could be null. We create it using Now or a regular DateTime in the constructor, and get DateTime values again with members like UtcTime or ToLocalTime() and more. No fancy stuff actually. We map it using a component every time (there are two properties to map). This could probably be easier with some NH feature (custom type?), but I didn’t have the time to care about this until now.

]]>