[johntgardnerjr]

We have a fairly large build where a main .bld file calls other .bld files. The problem we are having is that in one particular .bld file if a failure occurs, the build correctly stops, calls the failure steps and then says "build completed successfully" the caller thinks that everything went fine and runs until it needs something from the failed build and it finally fails.

Most of the called .bld files work correctly, i.e. if they fail the caller fails too. But one in particular does not, it can fail but the caller continues. We've examined and re-examined and I'm not ignoring failures. The biggest difference between the .bld files that work properly, and the one that doesn't is that the one that doesn't has failure steps. The .bld files that do work ok do not have failure steps. So it almost looks like if you do failure steps that VBP thinks the problem was handled and it can say everything is OK.

If this is the case, this seems counter-intuitive (ie bug). I didn't see that the documentation indicated this behavior.