TFS build doesn't clean drop folder on build delete

I ran into interesting problem - deleting build didn't clean drop folder. Checked access rights - all correct. The problem was that on build definition I used short machine name for drops folder: 

When I changed it to fully qualified name like this:

problem disappeared!

May be somebody has same issue out there :)

TFS Build: Unable to read Code Analysis output report. Make sure that the directory is writable (default is the project output directory)

Yes, the problem is  CodeAnalysisLogFile setting in your .proj file. 
Yes, removing this setting will fix your build.

Going back to my previous post, which is related to the same setting http://il-adan.blogspot.com/2012/04/tfs-build-code-analysis-no-result-files.html, I did some more to figure out HOW actually this settings ruins it all.

If CodeAnalysisLogFile  tag is set in project file, when code analysis is called - it sends in parameter /out. For example, see in .proj file:



That means  code analysis run wil get such parameter as /out:"bin\Debug\TestApp.dll.CodeAnalysisLog.xml". And it is a RELATIVE path from the place where FxCorp is run from. In case of TFS build, FxCorp is run from project file location. But as we remember, TFS build outputs files to $Binaries$ folder, not to $Project_location$\bin\Debug, so, since $Project_location$\bin\Debug doesn't exists - BANG!

Btw, if you want to avoid this nasty setting to appear in your porject files, when create new building configuration select Copy settings from <Empty>, this will keep your .proj file clean.

 


For those projects which already have this setting, I created a build activity which parses project files and remove this setting. Works as charm.

What to write as a check-in comment

This is just a geeks-fun post :)
See what people write as a check-in comment:

http://whatthecommit.com/

This made my day!

Is your Visual Studio 2010 up-to-date?

Have you installed all the latest patches and updates for your Visual Studio 2010? Probably you do not know the answer, as many of us don't.
A very nice solution is out there now, which helps you being up-to-date with minimal effort!

http://geekswithblogs.net/terje/archive/2012/05/06/visual-studio-2010-version-and-update-information-tool.aspx

Hope you enjoy it as much as I did :)

TFS build: TF277000: Cannot add process template with duplicate server path

Ever seen something like that?


 
And then you go, and create a copy of existing template with another name, just to be able to use it?
Easy :)
When creating a build definition, if you already have a template and probably used it before - do not click New button, just click on combo-box and you will find it there!