Geeks With Blogs

Shawn Jamison
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 to see locally scoped variables.  

It would have been faster to write a new workflow than fix this one...
Posted on Thursday, January 8, 2015 10:55 AM TFS 2013 , Team Build , Build workflow | Back to top


Comments on this post: Team Build XAML and scoped variables.

# re: Team Build XAML and scoped variables.
Requesting Gravatar...
Variable scope burned me again!
This time the variable name was reused in a different sequence with a different value
Left by And again on Feb 11, 2015 8:28 AM

Your comment:
 (will show your gravatar)


Copyright © Shawn Jamison | Powered by: GeeksWithBlogs.net