Timeline for answer to What are the reasons for rebuild and redeployment libraries? by Robert Harvey
Current License: CC BY-SA 3.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2014 at 12:22 | vote | accept | EngineerSpock | ||
| Mar 19, 2013 at 2:34 | comment | added | Agent_9191 | @EngineerSpock usually a switch statement will perform different logic based on an input parameter. If the cases are built around implementation classes, and a new class is added but the switch statement isn't, what should be the expected behavior? It's a violation of OCP and also means it's tightly coupled to the implementing classes. | |
| Mar 18, 2013 at 19:13 | comment | added | Robert Harvey | You'd have to ask Bob that. But generally too many dependencies are the cause. If there's no dependency on the other DLL, or your change isn't a binary breaking one, there's no redeployment of the other DLL needed. | |
| Mar 18, 2013 at 18:56 | comment | added | EngineerSpock | In one of the episodes Uncle Bob said that changing switch statement in one dll affects the depenedent dll and causes rebuild and redeployment. But why? Or maybe I just misunderstood his thoughts? | |
| Mar 18, 2013 at 18:44 | history | edited | Robert Harvey | CC BY-SA 3.0 |
added 328 characters in body
|
| Mar 18, 2013 at 18:19 | history | answered | Robert Harvey | CC BY-SA 3.0 |