What class in my project should responsible for keeping track of which Aggregate Roots have already been created so as not to create two instances for the same Entity. Should my repository keep a list
I have an application in which an Engineer accesses gas wells.He can see a list of wells by choosing any combination of 7 characteristics.The characteristics are company, state, county, basin, branch,
I\'m new in DDD. I 开发者_StackOverflow社区have a Topic entity and Lesson entity. Topic has many Lessons.
I have i discussion with a partner we have this scenario: **Publishers root entity Advertiser root entity**
The DataContext.GetTable() method will return an object of type: System.Data.Linq.Table By doing that, I presume I haven\'t issued a call to the database to retrieve the entire table.Otherwise, LINQ
Are there any sample applications available that show implementing DDD with Enterprise Libr开发者_JAVA技巧ary 5.0.if you have interesting then have a look this project
In the real world, Controllers can potentially need to use data from a variety of database tables and other data stores.For example:
I\'m trying to get EF4 working with ncommon 1.1 which provides DDD patterns such as UnitOfWork, Specification, Repository.
Given: You have an architecture with the layers presentation, business and data. You are applying domain-driven design.
VS 2010 / C# Trying to organize a solution and looking for options for naming the project that will host the interfaces for the repository.
加载中,请稍侯......