I see a lot of criticism of the anemic application model, so I decided to take this question.
I have two ASP.NET MVC applications that could share the same Models (they will use the same properties and methods)
Thinking not to rewrite or copy and paste all this people, I've been reading about the Repository standard in Macoratti's links (there are 3 articles link ), and I saw that there is a separation between the business rule and the properties, leaving the model closer to the anemic model.
I would apparently have solved my initial problem, as I would create a domain layer (Models), and a repository where I would put my BLL classes, with business rules and bank access, and could reuse those DLLs on my other site. >
Can anyone show me what the bad points are? As well as if I am not confusing myself on the default Repository? Or is there another exit so I do not have to rewrite all these classes?