Definición de compilación de TFS 2010: copiar dependencias a la carpeta de destino de compilación

I have a solution with many projects. Some of these projects have references to various 3rd party dependencies. These dependencies are in source control ($\ProjectName\BranchName\Dependencies). Building the solution works fine from Visual Studio.

When I create a build definition to build the solution, it fails when it tries to build the projects with the 3rd party dependencies. From the error messages I get (Could not locate the assembly) I'd guess this is because it doesn't copy the 3rd party DLL's into the target folder.

How do I get it to copy these dependencies from the location in source control into wherever TFS's build agent compiles my projects?

preguntado el 09 de marzo de 12 a las 13:03

1 Respuestas

After digging around a bit more, in the build definition there is a Workspace section where you can specify what source you want put where.

All I had to do was specify that my Dependencies were to be output to $(BuildDir)\Binaries and my problems were solved.

respondido 09 mar '12, 14:03

There you go! Additionally, you could consider using NuGet feeds internally to both publish new versions of dependencies and have them resolved during the build process appropriately. It's a great way for managing dependencies! - Ed Blankenship

No es la respuesta que estás buscando? Examinar otras preguntas etiquetadas or haz tu propia pregunta.