• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 198
  • Last Modified:

How do I stop a reference to an assembly being changed when adding another reference that also uses the already referenced assembly

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?

Thanks
0
CyLex
Asked:
CyLex
1 Solution
 
123654789987Commented:
First add a reference of assembly D. Then try adding a reference of Assembly B and c
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now