Databases
StackOverflow2013
Postsdbo
POADO.NET DbContext Generator vs. ADO.NET Poco Entity Generator (ObjectContext)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POADO.NET DbContext Generator vs. ADO.NET Poco Entity Generator (ObjectContext)
    primarykey
    data
    text
    <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="http://rads.stackoverflow.com/amzn/click/0596807260" rel="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>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRuben Bartelink
    1. USNelson Reis
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POADO.NET DbContext Generator vs. ADO.NET Poco Entity Generator (ObjectContext)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POADO.NET DbContext Generator vs. ADO.NET Poco Entity Generator (ObjectContext)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POADO.NET DbContext Generator vs. ADO.NET Poco Entity Generator (ObjectContext)
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO[very tangentially] related (Linq to Sql): http://stackoverflow.com/questions/3471455/is-dbcontext-the-same-as-datacontext
      singulars
      1. POADO.NET DbContext Generator vs. ADO.NET Poco Entity Generator (ObjectContext)
      1. USRuben Bartelink
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload