Timeline for Where to put business logic in MVC design?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 12, 2015 at 18:31 | comment | added | xr280xr | I agree. You get a much more flexible application when your model is simply a data structure acted upon by other business logic classes. As a simple example, I think that is a big failure of ASP.NET's approach to validation by using attributes. If I annotate a Person's FirstName property with the Required attribute, what happens if I create an admin view where FirstName should not be required? A business logic layer should consume the model and determine the appropriate actions for it. | |
| Sep 20, 2012 at 10:57 | review | First posts | |||
| Oct 10, 2012 at 20:31 | |||||
| Sep 20, 2012 at 10:56 | history | answered | MontyPython | CC BY-SA 3.0 |