问题
I am trying to follow Domain Driven Design using VS.NET 2012 & EF5.
I might have more than 250 Tables (and similar number of POCO Entity classes). If I decide to keep policy/rules/validation, all in one project/.dll, it is gonna be very hefty .dll and multiple developers working on same domain project will make it difficult to work together.
To keep Domain Layer Manageable:
- I divided it into different Modules. Each module have it's own Domain project & Service Layer.
- All the modules will have common single Infrastructure project which will have EF CodeFirst DataContext/Mapping classes.
- Now each domain object belonging to different modules requires to
refer each other as there could be relationship between these, and It might cause Circular Dependency problem.
Any way to avoid Circular Dependency problem.
来源：https://stackoverflow.com/questions/11502929/ddd-modules-and-ef-code-first