As I\'m working through my first large project with an ORM, I\'ve started to realize that the ORM will be a big impediment to creating domain objects that are expressive and that convey intent.
I need some help clarifying how I should be setting up my project. My solution structure is as follows:
i\'m wondering if there is a pattern how to separate the domain logic of a class from the ui responsibilities of the objects in the domain layer.
I\'m attempting to synthesize what I\'ve been reading about domain driven design and the entity framework model-first capabilities.I have an existing database, but I ignored that while I created my do
I mean - 开发者_如何学编程physically, in code. Organization of naming, namespaces, folders, assemblies, database/s.
We have a big object graph with lot of properties and behavior in it. We are currently revisiting our domain and we are going to go the DDD approach. But we are in need of a suggestion from you expert
I need to use LLBLGEN or EF4. I know that it is possible to use poco with EF4, however I need to use general approach.
My understanding of Domain Services is that they perform tasks that are outside the boundaries of the related repository (CRUD related tasks).
I\'m designing a desktop application with multiple layers: the GUI layer (WinForms MVP) holds references to interfaces of adapter classes, and these adapters call BL classes that do the actual work.
Say, for example, that I have a PostsService that creates a post: public class PostsService : IPostsService
加载中,请稍侯......