They are there. Off the top of my head, "/h" maps to InstallAction.Help and "/s" maps to "Display.Quiet". You can ignore the standard and make them mean whatever you want them to mean... although that's awfully weird and not at all recommended.
_____________________________________________________________ Short replies here. Complete answers over there: http://www.firegiant.com/ -----Original Message----- From: Marco Tognacci [mailto:mark...@live.it] Sent: Monday, March 2, 2015 3:53 PM To: WiX - users Subject: Re: [WiX-users] WiX Burn Command Line Options But the commands like /h or /s don't arrive in the Command parse function available in the BurnApplication as they are processed from the Base class and update the State of the application, for the variables defined in the Burn Bundle there is not a way or a special syntax for let the base class processing and updating the variables without the need for parsing the command lines (using the function of the Command object) For the variables the only way is to use the Command objects functions to parse each variable and set them, could you add a way for doing this by the Engine and Base class in the next version? (perhaps adding a parameter in the Burn Bundle variable)? Thanks ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
