Clever Geek Handbook

MySql.Data DLL not copied to output directory

A similar question was asked here without any answers. I have a cs project with a link to MySql.Data.Dll with CopyLocal = true. When I run msbuild from command line on the same computer (Windows 7 64 bit) it works fine.

When I run the same MsBuild on another computer (Windows Server 2008 RC2), the DLL is not copied to the output directory. Other copy-local DLLs are copied without issue and no error is printed. I have DLL access permissions and copying is done manually.

Does anyone know why this is happening / how to get around?

+2


source to share


2 answers


MySql.Data.Dll might be in the GAC on a Win 2000 RC2 machine rather than a Win7 machine, which could explain different behaviors.



+2


source


This may not be relevant, but I saw a similar problem when I moved the dll to handle the project reference. It will build fine locally, but will not copy the dlls on the TFS machine. It turns out I had to remove the original dll reference directly in csproj so that it knew to copy it through the project reference.



I can't remember the problem anymore, although that isn't much of an answer.

0


source






More articles:


All Articles