Effective Thoughts

In my experience, there's a lot of animosity and poor communication between Development and QA . It's not that they don't appreciate one another so much as they never seem to stay on the same page. QA : "What's the status on defect #4874?" Dev: "Done." QA : "Done?" Dev: "Yeah, I fixed that Tuesday." QA : "Err, ok . Well where is it? I mean where can I verify it?" Dev: "No clue. I committed it Tuesday. It passed unit tests and built successfully." QA : "Alright. I'll track it down." Invariably , QA speaks with the build manager (if there is one) to find the build in which that defect was repaired. After discovering the correct build, now QA needs an environment stood up to house that build. But wait, the UAT environment is currently testing the next release. It can't be disturbed for another week. At this point, the QA person's blood pressure heads for unsafe levels and the Dice.com bro...

By default, Team Build (MSBuild-driven) wants to output compiled assets (assemblies, config, exe's, etc.) to a flattened ..\Binaries\Release|Debug directory. I had a client desiring to package up these assets in their relative, normal output directories into an MSI using WiX. Fortunately, there's a simple directive to set within the TFSBuild.proj file such that the individual project OutDir is honored: true Set this within the main PropertyGroup element for your build. Unless you're performing a custom check-out, you'll also need to turn off read-only attributes set during the Get from version control. Update this attribute in the AfterGet target using an Exec task: