Many setup programs can take setup parameters, such as /silent and other flags to control the installation process. The provider of the setup program controls the flags accepted (if any) and what they do, you would have to get that information from the product vendor.
As far as using macros to control the setup flags that are passed when executing, this can certainly be done with Visual Build Professional.
As an example, I'll assume you are running a file called
setup.exe, and you want to optionally pass a parameter:
/param1. You could define a macro called
PASS_PARAM1, then assign true or false to it...
The Run Program step that invokes the setup program could have a command value of:
Code:
setup.exe vbld_IIf(%PASS_PARAM1%, "/param1", "")]
Of course that is a simple example but should get you started. Hope that helps...