How do I stop a reference to an assembly being changed when adding another reference that also uses the already referenced assembly
Posted on 2004-09-06
Environment: VB in VS2003 using Framework 1.1
To illustrate my problem: I have assemblies (dll) A, B and C. Assembly A has a reference to C. B also has a reference to C. For debugging both A and B have their reference to D set to ‘copy local = True’.
In my application I add a reference to assembly D. When I add a reference to B or C I get a message that the reference to D has been changed. The location of D is then changed to the bin of either B or C.
The result of this is that the application is not working with the newest version of C but with the newest version of C in the bin folder of either A or B.
I have removed the reference path in the application properties but this does not help as when you add the reference the path is also added automatically.
This is driving me nuts. Is there any way of stopping VS from automatically adding the reference path to the project properties? Is there another way of solving this problem?