Entity Framework Models

  • Thread starter Thread starter CT3
  • Start date Start date
C

CT3

I posted earlier on this and have not seen any responses. If there is
somewhere else I should post please let me know. I have read all of the MSDN
documentation I could find on EF but it is still unclear to me whether the
recommended practice is to have a single EDMX file in my data access
layer/business logic component or if I should (or even if it is possible) to
have more than one file.

Anyway, any general advice, pros/cons, etc. on having multiple models(?) or
edmx files in a project would be greatly appreciated. Also is it possible to
have more than one EntityContainer in a single EMDX file (I think I read
somewhere this is not possible)?

Thanks,
-CT3
 
Hi,

I generally try to create as small models as possible to capture a
specific concept. I.E, more then one EMDX file. I'm in the midst of
writing an article about EF and modelling best practices that will be
published on dotnetslackers.com in the coming weeks where I touch,
amongst other, this issue.

--
Patrik Löwendahl
http://www.lowendahl.net
[MVP] [MCT - Enterprise Application Development]

CT3 skrev:
 
Patrik said:
Hi,

I generally try to create as small models as possible to capture a
specific concept. I.E, more then one EMDX file. I'm in the midst of
writing an article about EF and modelling best practices that will be
published on dotnetslackers.com in the coming weeks where I touch,
amongst other, this issue.
Click to expand...

But what if you have relationships between entities in these models, so
effectively, they together form a connected graph?

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
Back
Top