Answered by:
TFS build Bin/DLL issue

Question
-
We are using Microsoft TFS 2012 update 4 and Microsoft VS 2012 ultimate update 5.
We are using TFS Build service.
After successful build it crates two follwoing folder on TFS build agnet
C:\Builds\4\BullseyeEvaluation Performance Management System\BullseyePerformance\bin
C:\Builds\4\BullseyeEvaluation Performance Management System\BullseyePerformance\src
In "C:\Builds\4\BullseyeEvaluation Performance Management System\BullseyePerformance\src\Source\Bin" it will not copy all DLL as in "C:\Builds\4\BullseyeEvaluation Performance Management System\BullseyePerformance\bin", which cause after build deployment my application because refrence/DLL not found in "Source\Bin" on web/application server.
See below snapshot
ABDUL HAFEEZ MCSE MCITP
Tuesday, December 1, 2015 8:08 AM
Answers
-
Hi ABDUL,
Are source and Bin folders under solution or project? If so, please right click the files=>Properties, then change Copy to Output Directory to Copy if newer.
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.- Proposed as answer by Starian chenMicrosoft contingent staff, Moderator Wednesday, December 9, 2015 8:46 AM
- Marked as answer by John QiaoModerator Thursday, December 17, 2015 2:06 AM
Tuesday, December 8, 2015 8:31 AMModerator
All replies
-
Hi ABDUL,
Thanks for your post.
This folder “C:\Builds\4\BullseyeEvaluation Performance Management System\BullseyePerformance\bin” is your solution’s binaries folder on your build agent machine, and this folder “C:\Builds\4\BullseyeEvaluation Performance Management System\BullseyePerformance\src” is your solution’s source folder on build agent machine.
All the files in binaries folder will be copied to drop location folder(configured in build definition) after TFS build. Files in binaries folder not be copied to folder “C:\Builds\4\BullseyeEvaluation Performance Management System\BullseyePerformance\src\Source\Bin”.
You should get that all dlls from binaries folder or drop location folder after build.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.
Wednesday, December 2, 2015 5:33 AMModerator -
I publish after successful build with following msbuild Argument in the build definition.
msbuild Argument => /p:DeployOnBuild=true;PublishProfile="Test Local"
which cause application crash due to missing DLL.
How I can automate, copy of all dlls from binaries folder or drop location folder to "src\Source\Bin" after build?
ABDUL HAFEEZ MCSE MCITP
Wednesday, December 2, 2015 9:39 AM -
Hi ABDUL,
Thanks for your reply.
Why there’s a “src\Source\Bin” folder under xxx\src path? This folder be created during your TFS Build or you manually created it?
You need change the path in your deploy argument to load dll files from binaries folder or load from src\solutionname\projectname\obj\Debug(Release)\ folder on your build agent machine.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.
Thursday, December 3, 2015 5:21 AMModerator -
“src\Source\Bin” is created during TFS Build not manually.
How I can change the path in deploy argument to load dll files from binaries folder or load from src\solutionname\projectname\obj\Debug(Release)\ folder on your build agent machine?
ABDUL HAFEEZ MCSE MCITP
Friday, December 4, 2015 4:51 AM -
Hi ABDUL,
Thanks for your reply.
How did you specify that “src\Source\Bin” path in your deploy argument before? You provided the path in this which argument? You can share your full MSBuild deploy command line here.
MSBuild deployment command run on your build agent machine, and that bin(binaries) folder generated on your build agent machine too, provide this binaries folder path your MSBuild deploy command.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.
Friday, December 4, 2015 9:36 AMModerator -
We did not specify “src\Source\Bin” path in deploy argument.
No provided the path in any argument.
See below snapshot of build definition.
ABDUL HAFEEZ MCSE MCITP
Friday, December 4, 2015 3:31 PM -
Hi ABDUL,
Could you reproduce that issue with a new project and a new build definition? You may share the sample project on the OneDrive, we will check it.
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.Monday, December 7, 2015 9:03 AMModerator -
same issue after new build definition.
We don't have any sample project, it is production source code we cant put on OneDrive
ABDUL HAFEEZ MCSE MCITP
Tuesday, December 8, 2015 4:33 AM -
Hi ABDUL,
Are source and Bin folders under solution or project? If so, please right click the files=>Properties, then change Copy to Output Directory to Copy if newer.
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.- Proposed as answer by Starian chenMicrosoft contingent staff, Moderator Wednesday, December 9, 2015 8:46 AM
- Marked as answer by John QiaoModerator Thursday, December 17, 2015 2:06 AM
Tuesday, December 8, 2015 8:31 AMModerator