|
Hi, we have several hundred project files that we're trying to assimilate into a build process. Thus far, we've had to leave a couple best practices behind because of circular references (quite a few, and on occasion 5+ dependencies down); in essence, dictating in the build file a fairly specific build order. One of my larger problems is that there are project references throughout some of the projects and MSBuild naturally wants to build that dependency, however, we know that the dependency is circular, therefore we include the binary in a referenced folder (indicated to MSBuild in the AssemblySearchPaths element), and we do not want that dependency built at that time, we want it to use the old version... if it can. So, my question is two fold, A) should I invest the time to programmatically change project references to assembly references before each build and across all files and/or is there an alternative and B) if you were in this situation and fixing the circular references was not an option (at least for the time being it is not for us) is there a different route (best practice) you would consider.
Thanks
Zeb |