Entity framework: one large model or a set of smaller models?
We recently discussed approaches to using entity structure. We have a fairly large and complex n-tier based application that needs to be overhauled.
The question is, if we start using the entity framework, it would be better to create one large model or a set of smaller models based on functionality / performance.
I have my own opinions on this, but I would be interested to know what other people think.
Update (Nov 17, 2008): I am creating one model, wiping it out and recreating, etc. For small projects at home. Although I have not tried it, I suspect this approach will be slightly more complex if there are a large number of entity types involved.
Also, does anyone have any experience using ef with a large team using TFS or similar?
source to share
In my experience, I would just do one big database model. Otherwise, it can be difficult to determine which tables have changed. When I make changes to the database, I just drop all tables in the model and regenerate it.
Of course, I also didn't customize my model by adding the "entity" functionality to it (not sure how this works).
So, I'm not an expert on this, but I usually use LINQ-To-SQL Models / Objects instead of Entity Framework - it has worked better for me so far.
source to share