Our team uses SVN over a shared solution with multiple solution files to break down sub-applications and share common libraries at the same time.
We've been running into a problem since our upgrade to VS 2012 where when new dependencies are added to some of the projects in the solution that change the existing build order, when other team members update their local repositories the new build order is not reflected and they get compiling errors (specially after a clean & build) because of missing dependencies as they have not been built yet.
I've tried looking at the VS documentation but there doesn't seem to be a way to control when VS calculates that build order and it's obviously something stored in the user options for the solution or some other local file that we are not versioning (otherwise there wouldn't be a de-synchronization between the code and the build order after a repository update)
I have 3 questions:
1) Is there a way around this problem? I don't think our setup is too far fetched so I'm looking for something besides 'don't use version control or multiple solution files'
2) Is there any way to share the build order or to tell VS to re-calculate it every time the solution is loaded?
3) Is there any other way to trigger the recalculation of the build order on-demand besides removing and adding a dependecy on the projects in the wrong order?
Thanks!