I am trying to figure out how to manage our basic Visual Studio solution. In the solution, we must manage C ++ / CLI projects, native C ++ projects, C # projects, external dependencies (compiled C # assemblies with their dependencies), managed by other teams and often updated (along with their dependencies).
Each type of project can be dependent on each other (except, for example, C # or C ++).
Some C # projects have dependencies on external DLLs, which may require some other DLLs to work correctly.
So far, we have used the post-build steps to copy links to each project output directory (additional dependencies for C # libraries compiled from the outside and required C ++ DLLs). We would like to automate this process. There are many projects, and external DLLs are often managed by other teams (sometimes they add more and more dependencies), and we would like every change made by them to be automatically reflected in our main project.
Is there a tool, best practice for batch files, or something that won’t lose itself in this hellish addiction, and just do an svn update and a little configuration every time a new project is included in the solution?
One of my problems is that I have a C # project1.dll file that requires C # project1a.dll and C # project1b.dll, if my C # project2 requires project1.dll, I would rather not add project1a.dll and project1b.dll for links to project2, but I would like to find it in my output folder (this is because project1a is controlled by a different command, and you may need to work with project1x.dll every day).
How did you solve this requirement?
source
share