This documentation is archived and is not being maintained.

Warning: the dependency 'file' in project 'project' cannot be copied to the run directory because it would overwrite the reference 'file.' 

There is a conflict between dependencies; more than one distinct assembly files with the same name should be copied to the bin directory for the application to run. The run directory is able to resolve the conflict since one of the dependencies is a primary reference.

Double-clicking this Task List item will take you to the primary reference node that is conflicting.

This warning occurs when you have a dependency conflict but have worked around it by adding one of the conflicting dependencies as a reference. Or you may have had a version 1 reference, and then added a second reference which itself references the version 2 of the first reference.

That is, this error occurs because the projects in your solution have references to each other, but the references were created as file references (using the Browse button in the Add Reference dialog box), rather than project to project references (using the Project tab on the Add Reference dialog box). The advantage of a project to project reference is that it creates a dependency between the projects in the build system so that the dependent project will be built if it has changed since the last time the referencing project was built. A file reference does not create a build dependency so it is possible to build the referencing project without building the dependent project, and so a reference can become obsolete; a project can reference a previously built version of the project. This can result in several versions of a single DLL being required in the bin directory, which is not possible, and results in this error message.

This message appears every time there is a conflict in the bin directory and the application may not work properly. Even though you may have worked around this problem, this warning will still appear because the project system cannot determine whether the version of a dependency will work correctly with all components.

To correct this error

See Also