I am currently using msbuild to solve over 600 projects.
Imagine that I am changing the code for 1 library that is used by 10 projects. Instead of providing all 600 projects to msbuild and letting them compile them all and find out the dependencies. I was wondering if there is a program or library that I could use to analyze the dependencies of all 600 projects and let me only compile 11 that are needed.
In other words, given the input of all 600 projects for scanning, and BaseLibrary.csproj as a project that has been changed by the parameter, will provide me with only 11 projects that I need to compile as output.
I have experience writing custom tasks, I would rather use a third-party library to analyze the dependency, if already there.
My company releases incremental releases into production every 3-4 months. As an experiment, I wrote a custom task that looks at previous issues of the Subversion tag and evaluates all compiled files that have changed since then and compares them with the project.
The only use case I can think of does not work, the one I mentioned is where the base library is changed and the system is not aware of all the projects that depend on it.
source
share