Friday, March 04, 2005
"The dependency whatever.dll cannot be copied to the run directory because it would conflict with the dependancy..."
If you ever get a message along the lines of:
Warning: The dependency 'Foo, Version=1.0.1661.21305, Culture=neutral' in project 'Bar' cannot be copied to the run directory because it would overwrite the reference 'Foo, Version=1.0.1661.20048, Culture=neutral'
You can check out Scott Hanselman's site here for some tips:
Dependency Conflicts
In addition, you can also check the dependency list using ILDASM. If you open each dependent DLL in ILDASM and inspect the manifest, looking for references to 'Foo', you should be able to track down the assembly that is referencing the old assembly (in this case the 1.0.1661.20048 version of Foo). Usually the assembly is referencing a different version of the conflicting DLL (or the assembly is referencing multiple versions of the same DLL). Once you find the assembly, you can rebuild it or delete it from the bin directory and re-reference it.
Warning: The dependency 'Foo, Version=1.0.1661.21305, Culture=neutral' in project 'Bar' cannot be copied to the run directory because it would overwrite the reference 'Foo, Version=1.0.1661.20048, Culture=neutral'
You can check out Scott Hanselman's site here for some tips:
Dependency Conflicts
In addition, you can also check the dependency list using ILDASM. If you open each dependent DLL in ILDASM and inspect the manifest, looking for references to 'Foo', you should be able to track down the assembly that is referencing the old assembly (in this case the 1.0.1661.20048 version of Foo). Usually the assembly is referencing a different version of the conflicting DLL (or the assembly is referencing multiple versions of the same DLL). Once you find the assembly, you can rebuild it or delete it from the bin directory and re-reference it.
