if you have assemblies A, B, and C, and A depends on B and C depends on B
and A, then you can easily get this problem.
A's dependency on B is defined as a dependency on the DLL file, while B's
dependency is a project dependency, so it is updated with each build.
Problem is, when you compile C, it wants to put both A and B into the
project folder, which won't work, because A depends on a different version
of B than C does.
The way to fix this: go through your projects for A, B and C. Drop every
reference and recreate it. If you make a DLL reference somewhere, make the
same reference everywhere. You cannot mix and match.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"cmay" <cm**@walshgroup.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...
I have been having some problems lately where I get the error where it
says that it cannot copy the new DLL b/c it will overwrite a reference
to the old version.
I know why this error happens, but often lately when I fix it, it
doesn't "work".
I have to manually delete dlls, restart VS.Net, close the solution,
stuff like that to get it to work.
Somewhere, something is getting heldup for whatever reason.
Is there any way to take a DLL and find its dependencies? When it says
that there is a reference to DLL XXX.XXX with version 1.123.1233.3211,
where is that information stored?
I tried looking at the DLL in ISDASM and tried looking at the project
file in notepad, but no luck.
How can I find these dependencies?
