I want to specify entity namespace based on my domain structure. Usually like that : Infrastructure.SqlServer
Given an application that involves, say, Companies, I might have a Company class. I will have a data access layer that populates a List &l开发者_运维问答t;Company>.However, there will be times (suc
In the context of DDD how is everyone physically structuring their files/folders when it comes to bounded context and aggregate roots?
Entities and value objects are both domain objects. What\'s开发者_如何学Go the use of knowing the distinction between the two in DDD? Eg does thinking about domain objects as being either an entity or
We have a class Event (it\'s actually named differently, but I\'m just making abstraction): public class Event
Being confused again after reading about this anti-pattern and the many concerns about it here on SO.
Inspired by the DDD hype, I designed my classes pretending there was no database at all. And then used NHibernate to map the classes to database tables. Part of my class graph look like this: Order (h
Although BindingList<T> and ObservableCollection<T> provide mechanisms to detect list changes, they don\'t support mechanisms to detect/intercept changes before they happen.
After spending a couple months studying DDD methodology, I\'ve now began to apply these concepts into actual products at my company.In fact, I\'ve been tasked with creating a suitable and maintainable
Just wanted to get the groups thoughts on how to handle configuration details of entities. What I\'m thinking of specifically is high level settings which might be admin-changed.the sort of thing tha
加载中,请稍侯......