This often happens when developers leave wildcard asterisks in the
assemblyinfo file build version string - it gets incremented every time you
do a build. If developers' build versioning gets out of whack, there's the
source of your problem.
You can delete the "supposedly" newer assembly from the output directory
before doing your build as a quick fix. But the best fix is to have a good
build versioning protocol that everyone understands so the issue doesn't
happen in the first place.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Ab******@gmail.com" wrote:
Hi,
I got an application which incorporate many other dll controls. When I
integrated the builds from other person, I get this error all over the
place
Error: The dependency 'MyDAL, Version 1.0.2482.21839, Culture=neutral'
in project 'Controller' cannot be copied to the run directory because
it would conflict with dependency 'MyDAL, Version=1.0.2475.19815,
Culture=neutral.
I got many more of these when adding the new MyDAL project to my
application. How do I fix this?
Thanks