We are using the single master solution strategy in more than one software project, and recently somebody added a dependency in common code which broke the other project's solution until the new dependency was added to their solution. What's a good strategy to eliminate or minimize this kind of issue?
We've thought of the following:
- Add a keyword to the checkin log message to tell other projects to add the dependency (but this is a manual process)
- Work with multiple partitioned solutions instead of a single master solution (resulting in longer build times, loss of intellisense across solutions, etc.)
- Use a tool to create a master solution from multiple partitioned solutions (any suggestions that work with VS2015, and can this be automated?)
Our largest single master solution so far is 115 project files, so on that basis alone it doesn't seem like partitioning the solution is necessary unless that's the best way to solve our problem.
If you have run across this problem, how did you solve it?