Note that there are some explanatory texts on larger screens.

plurals
  1. POTeam Build doesn't create the bin folder and the linked assembly
    primarykey
    data
    text
    <p>I want to use TFS Team Build, and have created a build definition. The trigger is gated check-in.</p> <p>When I check in the code, the build fails and I face the following error:</p> <blockquote> <p>C:\Program Files\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets (177): Unable to copy file "bin\OTS.RMS.DomainModel.dll" to "C:\Builds\1\OTC-RMS\Main Build\Binaries_PublishedWebsites\WebUIController\bin\OTS.RMS.DomainModel.dll". Could not find file 'bin\OTS.RMS.DomainModel.dll'.</p> </blockquote> <p>Some information regarding the project:</p> <ol> <li>OTS.RMS.DomainModel.dll is a class library that has my business logic code</li> <li>WebUIController is an MVC project</li> <li>I use Visual studio 2010 and TFS 2010 </li> </ol> <p>I've tried many solutions. One was to check-in the bin folder with its DLLs into source control. When I do that, the build succeeds, but I shouldn't do that because for each build there is a conflict between my local DLLs and the server DLLs. By default, the bin and the generated DLLs should stay out of TFS. </p> <p>After investigation on the TFS machine, I found the builds folder in the C: drive which will be used as a source folder. Team Build can get the source from the check-in and put this files inside this folder to start build it.</p> <p>I don't know why Team Build didn't create the bin folder and the DLLs as a result for the build and start copying the DLLs to the binary folder as needed.</p> <p>What could be the problem here?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload