title: Entity Framework and SqlDateTime overflow best practices
body: <p><code>System.DateTime</code> can take a wider range of values than SQL Server's DateTime.  Hence there is class <code>System.Data.SqlTypes.SqlDateTime</code> which mimics the later.</p>
  
  <p>Consequently I would have expected Entity Framework to choose SqlDateTime, but it didn't.</p>
  
  <p>So my questions are... </p>
  
  <p>What are the best practices to insure that your DateTime values will not cause problems when you try to save them to your database?</p>
  
  <p>Is there any way of forcing EF to use SqlDateTime?</p>