I\'m looking for some advice on how much I should be concerned around avoiding the anemic domain model. We are just starting on DDD and are struggling with analysis paralysis regarding simple design d
Closed. This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this po
I\'m trying to build my first CRUD application, and I don\'t understand if I should use an object containing getters and setters separated.
I am constructing an object using data f开发者_如何学Gorom a database table by passing the primary key of the row of data I want to use to construct the object.
I have been learning C# for the last year or so and trying to incorporate best practices along the way.Between StackOverflow and other web resources, I thought I was on the right track to properly sep
given the deprecation of loads of design patterns because of the new improvements in the Java EE world, DTO\'s are largely frowned upon.
In Entity Framework, is it possible to make the framework inject the DbContext into each object (entity) that is attached to or retrieved from the Context?
I am trying to understand Anemic Domain Models and why they are supposedly an anti-pattern. Here is a real world example.
Which metric(s) could help to indicate that开发者_开发百科 i have procedural code instead of object-oriented code? I would like to have a set of simple metrics, which indicate with a high probability,
Being confused again after reading about this anti-pattern and the many concerns about it here on SO.
加载中,请稍侯......