Ok, It actually went through the whole build when I added the statement:
Application.Options.RunProgramOutputWaitTimeout = 1000
Application.Options.RunProgramInputWaitTimeout = 1000
which was exciting. So I ran it again this morning, but it hung one step after the last hang. So it seems like it didn't "fix" it. May have moved it.
I'll try the next two steps. However I am not sure what is meant but a "chained" child. (other than what i would like to do to my 2 yr old sometimes
. Is a chained child a subsequent call to another .bld file? If so I don't have one so wont do step 4.
doing step 3:
3) Removing the VBP DEP exclusions (Control Panel -> System -> Advanced -> Data Execution Prevention -> Turn on DEP for all programs and services except those I select, Remove Visual Build Professional and Visual Build Professional 6 Console App from the list, OK, and restart Windows) and then configuring Windows to 'Turn on DEP for essential Windows programs and services only' (in that same dialog) and restart again.
4) Adding a Wait step (5 seconds) at the end of a chained (child) build.