Hello All

Is there a way to get a list of all available custom arguments to throw after a MSI file?
I deploy more and more MSI files, and it is starting to bother me to contact the vendors if i need information about this. For instance programs that needs some weird serial/servername arguments.

Thanks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Public properties will be possible but I think you're stuck with that.
Wouldn't we all love to know exactly what the vendor has thought about during their MSI authoring.
Answered 02/25/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: Beastie
Is there a way to get a list of all available custom arguments to throw after a MSI file?
I deploy more and more MSI files, and it is starting to bother me to contact the vendors if i need information about this. For instance programs that needs some weird serial/servername arguments.
It should be pretty straightforward to edit one of the scripts in the SDK to produce a list of an MSI's public properties.
Answered 02/26/2008 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

ORIGINAL: Beastie
Is there a way to get a list of all available custom arguments to throw after a MSI file?
I deploy more and more MSI files, and it is starting to bother me to contact the vendors if i need information about this. For instance programs that needs some weird serial/servername arguments.
It should be pretty straightforward to edit one of the scripts in the SDK to produce a list of an MSI's public properties.



Hi, sorry for the late response :-)
How would I do this? How do I see the scripts in a MSI file?
Answered 03/10/2008 by: Beastie
Yellow Belt

Please log in to comment
0
ORIGINAL: Beastie
How would I do this? How do I see the scripts in a MSI file?
Perhaps I didn't make myself clear. Download the Windows Installer SDK from Microsoft. That will install a bunch of scripts. I forget the target folder name - search for WI*.VBS on your local drive and it'll find them.
Answered 03/10/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity