Timeline for Organizing solution / project structure and classes for Line of Business Application (LOB)
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 19, 2014 at 9:22 | comment | added | Marjan Venema | In this case I don't agree with the YAren'tGNI approach. Separation of concerns is far easier to achieve and keep up when unrelated code is in separate assemblies. And of course separation of concerns helps achieving better design with high cohesion and low coupling. Having to add an assembly in your references makes dependencies visible and makes it harder for dependencies "to creep up on you". Use it to think about whether you actually need that code and/or whether is is where it belongs. It's a LOT simpler to code this way than having to loosen badly intertwined dependencies when YAreGNI. | |
| Jul 18, 2014 at 18:15 | history | answered | Dan Lyons | CC BY-SA 3.0 |