- e.g. From http://stackoverflow.com/questions/690033/best-practices-for-large-solutions-in-visual-studio-2008
- CopyLocal? For sure turn this off
- Always set the Copy Local property to false and enforce this via a custom msbuild step
- My advice is to always set ‘Copy Local’ to false
Some time ago we’ve tried to change the setting to false, and found that it causes problem for deployment of top-level projects.
Recently I’ve followed the suggestion and changed the settings for middle-level projects. It didn’t cause immediate issues, but I was warned by Readify consultant colin savage about possible errors during deployments.
I haven’t undone the changes immediately and we found a few issues during testing.
There are many scenarios, when you need to have Copy Local’ left to True.
The concerns are highlighted in some StackOverflow answers, but they have small number of votes.The concerns are highlighted in some StackOverflow answers, but they have small number of votes.
Top-level projects: set copy local = true.
- for all the references in the one at the top set copy local = true.
If you set ‘ Copy Local = false’, VS will, unless you tell it otherwise, place each assembly alone in its own .binDebugdirectory. Because of this, you will need to configure VS to place assemblies together in the same directory. To do so, for each VS project, go to VS > Project Properties > Build tab > Output path, and set the Ouput path to ..binDebugfor debug configuration, and ..binRelease for release configuration.
Second-level dependencies: set copy local = true.
Another example when copylocal =false fails on run-time, is when top level assembly doesn’t directly referenced one of indirect dependencies.
E..g. Top-level assembly A has reference to assembly B with copylocal =true, but assembly B has reference to assembly C with copylocal =false. Most likely assembly C will be missing on runtime and will cause errors
Copy local is important for deployment scenarios and tools. As a general rule you should use CopyLocal=True
Unfortunately there are some quirks and CopyLocal won’t necessary work as expected for assembly references in secondary assemblies structured as shown below.
This makes xcopy deployments difficult .
The fix for the issue is recommended in http://stackoverflow.com/a/6200173/52277