Custom Error Codes for Chained Programs
Instead of "failing" and stop running on all non-zero return codes, allow acceptable return codes to determine if the install sequence fails or continues. Example, uninstall an MSI to be sure it's not there but if it's not, generates a 1605 return, yet this is really a soft error which we currently have to use a BAT or VB script so we don't get a "failure". It should be up to the engineer to determine what is and is not a "failure". Of course, out of the box any non-zero should continue to be a failure.