On 28/06/2012 14:10, Brian C wrote: > More information... > > If I pass "/?" on XP or Win7, I get "ignored" as the command line argument. > If I pass obvious variables (i.e. INSTALLDIR=<path>), then those arguments > are passed through along with the "ignored" string. The Command.CommandLine = > "ignored INSTALLDIR=<path>", so I could hard-code that if we are running on > 64-bit, just always ignore the "ignored" string, but that would prevent > distinguishing between no command line argument and the '/?' argument.
As far as I know a custom BA is responsible for displaying help if passed "/?" - it's not handled by Burn. Standard parameters like /passive, /quiet etc. are handled and your BA doesn't see those in the array of command line arguments, but it's up to you to do a MessageBox, printf etc. if you get /?. -- Bruce Cran ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
