>I've inherited a large ASP.Net app (149 projects in 6 soultions). I'm trying to get a clean build of all the solutions with no luck. Most of the problems are related to file references in projects that point to assemblies in the other solutions. Solution A depends on an assembly in Solution B. Solution B depends on an assembly in Solution A. Not really circular, but I generate DLL version warnings (and occasionally errors) when I perform a build. The errors go away when I set 'Copy Local' to false on the File References.
>
>MS documentation states "If the project contains a reference to an object that is not in one of these locations, the reference must be copied to the output path of the project when the project is built. The CopyLocal property indicates whether this copy needs to be made".
>
>I would think if the project has a fully qualified path to the assembly, Copy Local could be False for the build. What problems will I encounter by setting "Copy Local" to false? (The other developers just ignore the warnings but that practice has always bothered me.)
>
>Thanks
What problems will I encounter by setting "Copy Local" to false - None, if you have all of the references to the many different projects locations and Alot if you do not. One way, I do it is that I compile all of my re-compile all of my projects with "Local" true so that I can get a local reference of all the needed "dll" and place them into a single "\bin" directory, or I would use the gacutil to place all of my dll projects into the GAC.

Hope this helps