I am OFFICIALLY not a fan of team builds XAML scoped variables.I just spent two weeks troubleshooting a weird build issue to find out that a block of workflow sequences were copied and pasted into this build. Both sequences have many of the same variable names but different scopes. The way VS shows them to you would never know that you have 5 OUTPUT_CARD_ROOT variables with 5 different scopes and values unless you are lucky reading the raw xml.Not a fan of a visual editor that assumes you only want ......
I have TFS build workflows that are causing me some headaches right now. They do what they are designed to very well and for non Microsoft technologies. They just were not designed to have new builds with different compilers added easily. In one workflow adding a project to build is easy. Add the project file in the "Items to build" section of the build definition.The bad news. The for each statement that iterates through the "Items to build" are compile and copy blocks for every other build technology ......