title: ADO.NET DbContext Generator vs. ADO.NET Poco Entity Generator (ObjectContext)
body: <p>I am about to start implementing the data access infrastructure of a project that was architected with an approach to DDD (<em>it's my first attempt on DDD, so be gentle ;-)</em> ). </p>
  
  <p>I will be using Entity Framework. Until now, I was looking into the method teached by Julie Lerman on her great book, <a href="https://rads.stackoverflow.com/amzn/click/com/0596807260" rel="noreferrer" rel="nofollow noreferrer">Programming Entity Framework</a>, where <strong><em>ADO.NET POCO Entity Generator</em></strong> is used, with some changes to the T4 templates and some more custom code.<br>
  Today I started reading articles on EF4.1 and the <strong><em>ADO.NET DbContext Generator</em></strong>, using <strong><em>Database First</em></strong> approach, and I'm trying to decide with which one should I go.</p>
  
  <p>DbContext and EF4.1's approach on DDD seems to be a nice, cleaner way than POCO Entities, but I'm afraid that it could lead to some issues in the near future, since EF4.1 is still in RC.</p>
  
  <p>From <a href="http://blogs.msdn.com/b/adonet/archive/2011/03/15/ef-4-1-release-candidate-available.aspx" rel="noreferrer">ADO.NET team blog</a>, I know that EF4.1 <strong>does not</strong> include:</p>
  
  <ul>
  <li>Enum support</li>
  <li>Spatial data type support</li>
  <li>Stored Procedure support in Code First</li>
  <li>Migration support in Code First</li>
  <li>Customizable conventions in Code First</li>
  </ul>
  
  <p>From my understanding, since I will be using <strong><em>Database First</em></strong> there is a smaller number of features that were not included.</p>
  
  <p>In conclusion, my question is:<br>
  <strong>Can I replace <em>POCO Entities Generator</em> with EF4.1 DbContext Generator?</strong></p>