Geek Answers Handbook

Why doesn't my TFS trace collector work even though there is no Drops folder?

We have a small setup of the TFS 2013 server and launch builds for one project. For this project, we have only one build definition that disables the Drops function. That is, This build does not copy output files to a drop folder . However, we get this message every time we save the assembly definition:

This assembly spends time and computer resources because your work Folders include team projects (... Project), which include Drops. You must hide the Drops folders. See http://go.microsoft.com/fwlink/?LinkId=269693 .

Normally, I would run and close the Drops folder. But this makes the assembly hang at the very end (after completion, testing and deployment) immediately after the "Reset Environment".

My question is, why does TFS warn us to cover the Drops folder, even if it really isn't? Or is it, and I completely ignore it?

+6
source share
3 answers

I had the same problem and the solution above does not help, since Dylan Smith does not explain how to stop the warning when there is no Drops folder (empty or not), which is the problem in the original question. My solution to “hacking” was to create a Dummy Drops folder in the TFS root project and hide it.

+3
source

A workaround has been found for this: first, add the cloak directive to your non-existent Drops folder:

Cloak | $ [solution name] \ Drops

Save it, he will not complain. Queue to the assembly, and let it fail, because "Drops are not displayed." Go back to the Build definition and delete your Drops Drops folder, then save it. For me, I no longer receive a warning. Hope this works for other people!

+3
source

This is a problem because it means that TFS Build downloads not only your source code, but all the drops every time. Usually this is a waste, since you do not need to upload a folder with drops. In your case, the Drops folder may be empty, but the warning logic is not smart enough to figure it out.

0
source

More articles:


All Articles