I have a client -> service -> server,开发者_C百科 architecture and I want to introduce validation.
I was using State Pattern in a normal state machine. I wanted to be able to go from [A -> B], [B -> C], and [A -> C].
I am currently working on a project where I have a BankAccount entity for some other entity. Each bank account as a reference to a bank entity, an account number and optionally an IBAN.
We have a requirement to add an event reminder when a user enters their email address o开发者_运维技巧n an event page. Event is another domain object. Our initial thought was to create a Customer doma
I find that whenever I create a layer/tier, I have to translate between one layer to the other, does that mean it is a tightly coupled system?If I was to change a business logic, remove a field in the
What do you think of the following table mapping style for domain entities? class Customer { public string Name;
In the book .NET Domain-Driven Design with C# from Tim McCarthy there\'s an example of a link table (two foreign keys + one boolean column) that gets it\'s own class in the domain. Is this common?
I\'m using NHibernate to persist my domain objects. To keep things simple I\'m using an ASP.NET M开发者_如何学运维VC project as both my presentation layer, and my service layer.
Are there any best practices for syncing hierarchical domain objects between client with mo开发者_StackOverflow社区dular structure (WPF,PRISM,MVVM) and server(WCF service and NHibernate for persistenc
I\'ve got this question about form validation and business validation. I see a lot of frameworks that use some sort of form validation library. You submit some values and the library validates the val
加载中,请稍侯......