Dependency Error: The dependency <dll> in project <project> cannot be coppied to the run directory becuase it would conflict with dependency <dll>

[Jay A. Moritz]

Error: The dependency '<my dll>' in project '<my project>' cannot be copied
to the run directory because it would conflict with dependency '<my dll>'.
I am getting a dependency error building my application that was using some
other namespaces that I had built and incorrectly referenced to the dll
instead of the project, but I ended up removing the reference entirely but
my project keeps getting the error.

How do I tell my project to stop looking for a dll that isn't even
referenced anymore and stop giving me this <expletive removed> error?

Jay A. Moritz

[SemiproCappa]

Two things you could try:

1. Check that all the references paths in your project properties are
correct. Old reference paths can cause VS to pick up the wrong dlls

2. If that seems to be alright try deleting all the dlls in your bin
directory.

"Jay A. Moritz" wrote:

Error: The dependency '<my dll>' in project '<my project>' cannot be copied
to the run directory because it would conflict with dependency '<my dll>'.
I am getting a dependency error building my application that was using some
other namespaces that I had built and incorrectly referenced to the dll
instead of the project, but I ended up removing the reference entirely but
my project keeps getting the error.

How do I tell my project to stop looking for a dll that isn't even
referenced anymore and stop giving me this <expletive removed> error?

Jay A. Moritz

[Cor Ligthert]

Jay,

Mostly this error is gone when you do a restart of your computer. It happens
because you have locked that dll. You can search as well what locks it of
course.

Cor

[Jay A. Moritz]

I have already found the articles about deleting the bin and obj directories
and rebooting the computer, I have also tried creating a new project and
importing my class files and windows forms. The project no longer has any
references to the dll that keeps blowing up so I have no interest in mapping
references to an unused dll in my bin directory just so I can build a
project. How does a programmer work around this <expletive deleted> BUG!! I
can't build my project because it errors on conflicting dll's that are no
longer referenced or required. Where is VS storing these references so I can
go changed it? Anybody have any new ideas?

Jay A. Moritz
"Jay A. Moritz" <jm*****@predictableoutcomes.com> wrote in message
news:ua**************@TK2MSFTNGP15.phx.gbl...

Error: The dependency '<my dll>' in project '<my project>' cannot be
copied to the run directory because it would conflict with dependency '<my
dll>'.
I am getting a dependency error building my application that was using
some other namespaces that I had built and incorrectly referenced to the
dll instead of the project, but I ended up removing the reference entirely
but my project keeps getting the error.

How do I tell my project to stop looking for a dll that isn't even
referenced anymore and stop giving me this <expletive removed> error?

Jay A. Moritz

[Jay A. Moritz]

I have also created a new project (gave it the same name as the old
project), new class files and copied and pasted the code from the old
classes into the new classes and the task list is already showing that I
have conflicting dlls.

Jay A. Moritz
"Jay A. Moritz" <jm*****@predictableoutcomes.com> wrote in message
news:ui*************@TK2MSFTNGP14.phx.gbl...

I have already found the articles about deleting the bin and obj
directories and rebooting the computer, I have also tried creating a new
project and importing my class files and windows forms. The project no
longer has any references to the dll that keeps blowing up so I have no
interest in mapping references to an unused dll in my bin directory just so
I can build a project. How does a programmer work around this <expletive
deleted> BUG!! I can't build my project because it errors on conflicting
dll's that are no longer referenced or required. Where is VS storing these
references so I can go changed it? Anybody have any new ideas?

Jay A. Moritz
"Jay A. Moritz" <jm*****@predictableoutcomes.com> wrote in message
news:ua**************@TK2MSFTNGP15.phx.gbl...

Error: The dependency '<my dll>' in project '<my project>' cannot be
copied to the run directory because it would conflict with dependency
'<my dll>'.
I am getting a dependency error building my application that was using
some other namespaces that I had built and incorrectly referenced to the
dll instead of the project, but I ended up removing the reference
entirely but my project keeps getting the error.

How do I tell my project to stop looking for a dll that isn't even
referenced anymore and stop giving me this <expletive removed> error?

Jay A. Moritz

[Jay A. Moritz]

Found the culprit. Partner had referenced the bad dll in one of the classes
he had built that I was referencing. Would have been a WHOLE lot easier to
track down the problem if the IDE had said what object/class had the
conflicting dll reference instead of just stating that there was a conflict.

Jay A. Moritz
"Jay A. Moritz" <jm*****@predictableoutcomes.com> wrote in message
news:%2******************@TK2MSFTNGP10.phx.gbl...

I have also created a new project (gave it the same name as the old
project), new class files and copied and pasted the code from the old
classes into the new classes and the task list is already showing that I
have conflicting dlls.

Jay A. Moritz
"Jay A. Moritz" <jm*****@predictableoutcomes.com> wrote in message
news:ui*************@TK2MSFTNGP14.phx.gbl...

I have already found the articles about deleting the bin and obj
directories and rebooting the computer, I have also tried creating a new
project and importing my class files and windows forms. The project no
longer has any references to the dll that keeps blowing up so I have no
interest in mapping references to an unused dll in my bin directory just
so I can build a project. How does a programmer work around this
<expletive deleted> BUG!! I can't build my project because it errors on
conflicting dll's that are no longer referenced or required. Where is VS
storing these references so I can go changed it? Anybody have any new
ideas?

Jay A. Moritz
"Jay A. Moritz" <jm*****@predictableoutcomes.com> wrote in message
news:ua**************@TK2MSFTNGP15.phx.gbl...

Error: The dependency '<my dll>' in project '<my project>' cannot be
copied to the run directory because it would conflict with dependency
'<my dll>'.
I am getting a dependency error building my application that was using
some other namespaces that I had built and incorrectly referenced to the
dll instead of the project, but I ended up removing the reference
entirely but my project keeps getting the error.

How do I tell my project to stop looking for a dll that isn't even
referenced anymore and stop giving me this <expletive removed> error?

Jay A. Moritz