I am getting my feet wet with DDD (in .Net) for the first time, as I am re-architecting some core components of a legacy enterprise application.
What is the best way and why? V1: try { var service = IoC.Resolve<IMyBLService>(); service.Do(); } catch(BLException ex)
I\'m experimenting with DDD and EF 4.1 Code First. I have an Aggregate Root BlogEntry which looks simlar to this:
I\'m sorry but I\'m new to repositories patterns, unit tests and orm tools. I\'ve been researching on unit tests and the repository pattern, and arrived at some conclusions, I wonder if I\'m right.
I have a Person Entity in my domain, this person have Gender and Status property, this properties are ValueObjects?
I\'m using Entity Framework in my DDD Application where I have Domain, Infra and UI Layers. My Context Interface is here:
Is client code allowed to reference entities within an aggregate that is not the root? I have a Story (Root), Team (Entity) and TeamMember (Entity). I am trying to decided if the AddTeamMember method
Here is an oversimplified version of what I am trying to do. I have a Story that gets reviewed by a user and that user can add it to their ballot. The business rule is a story can ONLY belong to the
In the realm of DDD I like the idea of avoiding getters and setters to fully encapsulate a component, so the only interaction that is allowed is the interaction which has been built through behavior.C
Being accustomed to using services and the concise calls they provide to interfact with the business layer, I\'ve been wondering if this approach can be applied to the user interface.
加载中,请稍侯......