We are currently revamping our archi开发者_如何学运维tecture and design of application. We have just completed design of Data Access Layer which is generic in the sense that it works using XML and ref
I am new to DDD. I开发者_高级运维n my mini-project, I have a structure that looks like this (different from the actual names):
I\'m starting on my first business project (.NET) and am trying to follow DDD 开发者_开发百科principles. Are there any guidelines or common patterns for orgaining source code and namespaces?
i\'m having trouble writing integration tests which use a fake repository, For example : Suppose I have a classroom entity, which aggregates students...
Im fairly new with DDD and Im trying to use IOC in order to loosen up my tightly coupled layers :) My C# web application consists of a UI, domain and persistence layer. My persistence layer reference
I use rich domain model in my app. The basic ideas were taken there. For example I have User and Comment entities. They are defined as following:
I\'m developing an application using asp.net mvc, NHibernate and DDD. I have a service layer that are used by controllers of my application. E开发者_开发知识库verything are using Unity to inject depen
We are following Domain Driven Design for the implementation of a large website. However by putting the behaviour on the domain objects we are ending up with some very large classes.
I have a question that is more in the realm of design, th开发者_开发问答an implementation. I\'m also happy for anyone to point out resources for the answer and I\'ll gladly,
I have a few (hopefully) simple questions about aggregate roots in domain driven design: Is it okay to have an aggregate 开发者_StackOverflow中文版root as a property of another aggregate root?
加载中,请稍侯......