Timeline for Strategy for maintaining assembly references in TFS
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2016 at 18:06 | answer | added | xr280xr | timeline score: 0 | |
| May 15, 2012 at 15:45 | vote | accept | P.Brian.Mackey | ||
| Mar 7, 2012 at 17:18 | comment | added | nlawalker | Don't look at solutions as units of developer work, look at them as units of build. If Project A in Solution A depends on project B, and project B is actively being worked on by anybody, make it a project reference. If the guy working on Proj. A doesn't need to work on Proj. B, then he doesn't need to touch it. | |
| Mar 7, 2012 at 14:02 | history | edited | P.Brian.Mackey | CC BY-SA 3.0 |
added 167 characters in body
|
| Mar 7, 2012 at 13:48 | comment | added | P.Brian.Mackey | @nlawalker - In cases where project A in solution A depends on project B, yet project B is not being actively worked on while in solution A. | |
| Mar 7, 2012 at 5:38 | answer | added | Nick Nieslanik | timeline score: 3 | |
| Mar 7, 2012 at 3:00 | comment | added | nlawalker | "This isn't always a good idea or feasible". Not saying that you're wrong, but what makes you say this? If you have code that's being actively worked on, it should be referenced as a project reference. | |
| Mar 6, 2012 at 22:16 | history | edited | P.Brian.Mackey | CC BY-SA 3.0 |
added 129 characters in body
|
| Mar 6, 2012 at 21:47 | history | edited | P.Brian.Mackey | CC BY-SA 3.0 |
deleted 13 characters in body
|
| Mar 6, 2012 at 21:30 | history | asked | P.Brian.Mackey | CC BY-SA 3.0 |