Hi Rob
This sounds very familiar, and I wonder if you have referenced your library
projects as file references. That is, when you referenced the dll from one
project in another, did you add it as a file reference or a project
reference? If you did the former, you will frequently see the symptom you
are experiencing, as there is a bug in the VS IDE/compiler in this area.
Always reference other projects by they project file and not the dll; it is
the Project tab when you select Add Reference.
One other thing to be wary of is circular references. The IDE will not allow
project A to reference project B if project B already references project A,
but if you add a third project then you can have project A reference B, B
reference C, and C reference A. Apart from being symptomatic of a flawed
design, this can also cause havoc at compile time.
HTH
Charles
"Rob R. Ainscough" <ro*****@pacbell.net> wrote in message
news:OL**************@TK2MSFTNGP09.phx.gbl...
I keep getting this error message when I build my solution:
Error: The dependency 'xxx.xx.xx, Version=1.0.2067.27633, Culture=neutral'
in project 'xxx.xx.xx' cannot be copied to the run directory because it
would conflict with dependency 'xxx.xx.xx, Version=1.0.2068.11260,
Culture=neutral'.
I have a solution that contains 10 class library projects, some of these
projects require references to other projects within the solution.
xxx.xx.xx is the name of my DLL (class library).
I'm having a hard time even understanding why I'm getting these errors
that sometimes will go away if "build the solution" enough times (like 5
or 6 times).
I've tried disabling "Copy Local" -- this causes havoc in my ASP.NET
solution that uses some of these class libraries. I've tried clearing and
setting my solution/project dependencies but this has not helped. I've
also gone thru the class library bin directories and even deleted the
"copied" referenced DLLs the project requires and that works the first
time but anytime after that if I modified a project within the solution
and Build, the above errors come back.
This is VERY frustrating to deal with (I really do have better things to
do) and I've wasted many many hours/days trying to resolve this problem.
I'm at the point now where I'm thinking of writing a Macro to deleted all
my Copy Local DLL's, then do a new Build on my solution -- there must be a
better way??
Using VS 2003 (VB.NET).
Rob.
