I'm having problems with a large EDMX - the diagram is massive and difficult to navigate, but more importantly merging different branches of the project creates many conflicts, which is painfull when done regularly.
What I'd like is to split my EDMX into a core EDMX, and then other EDMXs for logical sections of the project, which usually have nothing to do with each other, except the shared core entities. I would like all of these EDMXs to output entity classes to the
same model project.
I've seen tantalizing mentions of splitting EDMXs in google, and possibly inheriting too, but no solid yes or no as to wether it can be done.
I'm using EF4 Self Tracking Entities, if that makes a difference.