I have plain POCO\'s here and as INotifyPropertyChanged is a Interface for the View\'s need its implemented in the ViewModel not the Model.
I\'ve seen a lot of codes use a service-dao pattern , I don\'t know the origin of this pattern . It force the front layer call service, then delegates some of the 开发者_如何学Cservice task to dao.
I\'ve always developed code in a SOA type of way.This year I\'ve been trying to do more DDD but I keep getting the feeling that I\'m not getting it. At work our systems are load balanced and designed
I am design and EMR. I have determined the central object to the domain is the Patient.The patient must have the following a Doctor and Medical Records.Medical Records is a grouping term refering to t
I\'m creating some business logic in the application but I\'m not sure how o开发者_Go百科r where to encapsulate it, I\'ve used the repository pattern for data access, I\'ve seen some projects that use
Should Domain Entities be exposed as Interfaces or as Plain Objects ? The User Interface : public interface IUser
I would like to do some exercice and apply DDD to my Domain Model applied to Northwind database. Even if Northwind is an example I imagine that it was done to satisfy some \" virtual business\" requir
I have an application that I\'m trying to build with at least a n开发者_运维知识库ominally DDD-type domain model, and am struggling with a certain piece.
I am reading the book Applying-Domain-Driven-Design-Pattern. In its model design, it ha开发者_JAVA百科s the Order hold reference to Customer,but if it was me doing the design, i will probably have th
Closed. This question 开发者_开发百科does not meet Stack Overflow guidelines. It is not currently accepting answers.
加载中,请稍侯......