asp.net - How mature & felxible is the Entity Framework's code-first library? -


i'm getting ready small, brief architecture spike using ef code-first approach, introduced scott gu here , here. before do, i'd know whether worth it. have project uses ef poco generation template, , i'd investigate advantages can out of switching more pure poco strategy domain model. particularly, these things i'm interested in:

  1. avoiding automatically-generated partial classes collection fixup methods, , being able concentrate on essential domain object code without worrying association persistence.

  2. avoiding having transform templates every time want add artifact model.

  3. still being able have control on strategy of table persistence (locations of complexttypes, table-per-type versus table-per-hierarchy, etc). these aren't important other 2 concerns.

the recent version find of ctp4, released summer 2010. current version?

what cons of choosing approach, using particular library? can recommend other concerns should investigate in spike?

go through these tutorials , check this blog additional topics inheritance - give pretty overview of code first in ctp5 should close final version stated here:

ctp5 our final preview of code first , simplified api surface (dbcontext) before offer full supported production ready release in q1 of 2011.

i think 3 points mentioned satisfied current version.


Comments

Popular posts from this blog

python - Scipy curvefit RuntimeError:Optimal parameters not found: Number of calls to function has reached maxfev = 1000 -

c# - How to add a new treeview at the selected node? -

java - netbeans "Please wait - classpath scanning in progress..." -