.net - Anyone using the Entity Framework *Well*? -


has shipped entity framework project o/r mapping conceptual classes quite different tables in datastore?

i mean collapse junction (m:m) tables other entities form conceptual classes exist in business domain organized multiple tables in datastore. examples see on msdn have little use of inheritance, collapsing junction tables other entities, or collapsing lookup tables entities.

i'd love hear of or see examples of below support crud operations typically expect on business object.:

  1. vehicle table , color table. color can appear in many vehicles (1:m). form conceptual class usedcar has property color.

  2. doctor, doctorpatients, , patients tables (form many many). doctors have many patients, patients can have many doctors (m:m). map out 2 conceptual classes doctor (which has patients collection) , patients (which has doctors collection).

anyone seen/done csdl , ssdl in entity framework? csdl no if doesn't actaully map anything!

i attempted use entity framework on existing project (~60 tables, 3 inheritance) see about. experience boiled down to:

the designer surface kludgy. mapping isn’t intuitive , must have thought having several tool windows open @ same time acceptable. took long time manually create object , map right fields – still odd talking code. while having handling database communication essential, i feel handing control on ef far more of fight doing manually.

sometimes designer doesn’t load until restart visual studio. i’m sure it’s bug restarting vs annoying.

all work ends in single file, i’d hate merge multiple developer editions.

the resultant sql (watched via profiler) wasn’t good. didn’t delve looking why, you’d pressed write worse on first attempt.


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -