Visual Studio stop on failure

There's a nice rant here about the amazing fact that in 2011, Microsoft's premier code development suite still can't figure out that, when you're compiling a multi-project solution, and project B depends on project A, and project A has failed due to compiler errors, then there is no point at all expending a lot of resources rebuilding project B — something "make" figured out some 30 years ago. I stumbled across the post in a search for that very option, certain that I must be "doing it wrong," and was astonished to find that this was in fact the case.