We have several external dlls being referenced in our Web Application Project. We have a deployment project for installing on the hosting servers. When we were using .net 3.5 and vs2008 the dll were being copied to the bin folder. Since we have upgraded to .net 4 vs2010 this no longer happens and we are getting servers errors since the references cannot be found.
CopyLocal is set to true, and i cannot find anything inside the web.config which suggest this is being set else where.
I am not sure how it was set up in the VS2008 but I am almost positive that you might have been using the Post-Build event command line. In there you can tell to copy the dlls you need for deployement. An example is given below:
mkdir $(SolutionDir)\Deployment
copy "$(SolutionDir)Your_Library_Name\Your_Dll_ForDeployement.dll"
$(SolutionDir)\Deployment\
Something weird had happened to my deployment project. When i saw it had no detected dependencies, I remove the primary output and re-added it. The dependencies are now showing up and being placed in the bin folder when installed.
I am getting exactly the same issue. We have a VS2008 project which references the EnterpriseLibrary. When we run our integrated build using TFS and our Web Deployment Project, all the dll's are copied over. When we upgraded to VS2010, TFS2010 and WDP 2010, some of the DLL's are missing. Strangely, this only occurs to some dll's and not others. For eample, we get the Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll copied in both cases, but not the Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.dll
As a workaround I copied the files accross using a "BeforeBuild" step.
It now seems to build OK.