I have an aggregate named Campaigns every with a root entity named campaign, this root entity has a list of attempts (entity)
This forms part of a series based around me getting my head around DDD :) Following on from a previous question, but the background knowledge is not needed: System consuming WCF services from another
The benifit of having repositories when using DDD is that they allows one to design a domain model without worrying about how objects will be persisted. It also allows the final product to be more fle
I am creating a Bug Tracker application (toy one) with DDD in mind. I have a BugRepository with methods like Add / Delete / Save and a user Repository having the same kind of methods (Actually both de
I am currently in the process of creating a Proof of Concept for a product/party administration system, based on the principles of DDD. One of the requirements is that the party data (customer, resell
I\'ve read DDD Evans, and I\' experimenting with an aggregate root repository design using C# and Entity Framework 4.1 + LINQ.
I would really appreciate peoples opinions on the below design problem. I have a model in which either a ‘Person’ or a ‘Business’ may be the provider of a certain ‘Service’. An example class d
I\'ve just begun to delve into my first experiments with Domain Drive Design and I\'m taking advantage of the NWorkspace pattern. This pattern seems to make a lot of sense however I haven\'t been able
What would be the drawback (in terms of testability for example) to the following approach which intends to get the best from Active Record pattern and Repository pattern ?
I have read that Windsor is the best DI/I开发者_StackOverflowOC tool to use so I figured I would give it a try. I am seeing many examples of how to wire everything up using and MVC project however I n
加载中,请稍侯......