Timeline for C#: Simplfy code using Interfaces + business rules / validation
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2012 at 12:24 | comment | added | Haroon | I have refactored, could you please comment? | |
| Jan 23, 2012 at 11:37 | comment | added | Haroon | point3 - handling exceptions: my asp.net mvc application will handle this, not my domain/core project, it is handled inside a filter globally, some errors will show up in UI, some errors will force a 404 - depends on what exception I am throwing, so there is no need to handle anything within these classes (unless it is relevant to the code creating/calling/depending on this class) | |
| Jan 23, 2012 at 11:34 | comment | added | Haroon | Yes I have been told there will be different higherlevel workflows - each with its own validation + rules (potentially), hence the need for an interface (I will resolve the higherlevel interface depending on certain variable) | |
| Jan 22, 2012 at 23:51 | history | answered | radarbob | CC BY-SA 3.0 |