I am getting confused between domain/application logic and User Interface logic.To illustrate what I am trying to nail down, I will describe an imaginary program below for illustration purposes:
This may be a basic question but I am pretty new to DDD. I have an domain object that we\'ll call Adjustment which can be processed in bulk from the UI. Before we process the Adjustments, we need to v
We\'re developing a DDD based system.For a particular module (the publisher) in that system, we will receive data from other objects and perform transformations on them, then write out data files.
The layering scheme for DDD suggests that the layers should be; Presentation/Application/Domain/Infrastructure
I\'m new to DDD so please forgive me 开发者_如何学Goif I\'m not using the terms correctly. I am Using C# MS/SQL and NHibernate.
In the consumer code? (like a controll开发者_开发百科er) In repositories? In services? For starters, that\'s a pretty controversial question, so you are bound to get many different answers.
We are currently finishing an architecture plan for a new software application we are developing next year in ASP.NET MVC / C#.
I am just at the brink of going \"Ah HA!\" when it comes to coding Domain Driven Design.The question is How and where to define a MVC ActionMethod parameter class that involves an entity, a value obje
I\'m curious if anyone has applied workflow foundation to a DDD project and if s开发者_C百科o what the pitfalls/gotchas were.
I\'m not well versed in domain driven design and I\'ve recently started created a domain model for a project. I still haven\'t decided on an ORM (though I will likely go with NHibernate) and I am curr
加载中,请稍侯......