I am trying to prevent Visual Studiofrom overriding my binary folder a project that is not supposed to be used during build. Display the following solution structure:
App1 -> LibB -> LibA
Every time I try to create a project LibB(build / rebuild), it replaces LibA.dllin my binary folder App1. The real problem is the different version LibA.dllused by App1and LibB. Imaging I have another project App2:
App1 -> LibB (v2) -> LibA (v2)
App2 -> LibB (v2) -> LibA (v2)
LibB (v2) -> LibA (v1)
And now every time I create a project App1, it destroys the binary folder of my project App2, because when the project LibBis created, it moves LibA.dll (v1)to my binary folder App2, which is not the expected behavior.
ps # 1: I can’t upgrade LibB (v2)to use LibA (v2)just because it is a simplified description of the problem, and there are many dependencies like the ones described above. Say this will be my long-term solution.
ps # 2: if you try to build a project LibB, it will update the binary folders App1and App2with the help LibA.dll (v1)and destroy both application projects.
ps # 3: I recreated a test solution with a similar dependency model and it works fine, so there is a problem with the existing solution that I am trying to fix.
How can I prevent a Visual Studioparent project from updating when creating a child project?