12/16/2009 2405 views
The client for which I am working, has a std of triggering installation through single line script. right now he is using script like below:

set shell1 = createobject("WScript.Shell")
shell1.exec "msiexec.exe /i test.msi TRANSFORMS=test.mst"

if i want to put patch in this script test1.msp, and test2.msp, from test1 and test2 folders respectively, then how can we write this script?
We have test.msi,test.mst, test1 folder[including test1.msp], test2 folder[including test2.msp]

please guide
0 Comments   [ + ] Show comments


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

All Answers

Only a fool patches clients.

Create an AIP, patch that, then run the patched package. You may want to back-up the unpatched AIP as I do, but, as I believe I may have mentioned, that may just be due to my paranoia.
Answered 12/16/2009 by: VBScab
Red Belt

Actually I directly merged 2 msp filesin to base msi, and it was running fine, but they do not want like that. They want it through script
Answered 12/16/2009 by: abking99
Second Degree Blue Belt

Part of your job as a packager is education. Just because they want it that way doesn't make it the right way. Hell, why even bother using MSI? What was wrong with XCOPY? Anyway...whatever...

Use the standard patch syntax: /P <path_to_and_name_of _MSP>;<path_to_and_name_of _MSP>;<path_to_and_name_of _MSP>
Answered 12/16/2009 by: VBScab
Red Belt

You can also use Wise Script to perform the installation.
Answered 12/16/2009 by: mekaywe
Brown Belt