Install isscript in another mst
Hello,
A question regarding isscript.
We have multiple apps which all uses a different version of isscript. So I made installscripts which first installs the proper version of isscript and after that, the vendor msi with a mst. So far so good.
Now we would like to have one vendor msi with a mst. And nothing more.
And now the question: in the mst:
- append the isscript files to the mst
- install isscript
- install the application
I played around in Wise Package Studio v5.60 but I did not get it working (only the first item worked).
Is there a way to get this done? (And not capture both the installation of isscript and the vendor MSI.)
Any help is appreciated. [:D]
With kind regards,
Willem-Jan
A question regarding isscript.
We have multiple apps which all uses a different version of isscript. So I made installscripts which first installs the proper version of isscript and after that, the vendor msi with a mst. So far so good.
Now we would like to have one vendor msi with a mst. And nothing more.
And now the question: in the mst:
- append the isscript files to the mst
- install isscript
- install the application
I played around in Wise Package Studio v5.60 but I did not get it working (only the first item worked).
Is there a way to get this done? (And not capture both the installation of isscript and the vendor MSI.)
Any help is appreciated. [:D]
With kind regards,
Willem-Jan
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
linstead
18 years ago
why you don't just run the vendor msi and make a transform from that msi
Posted by:
WillemJan
18 years ago
Hello Linstead,
Thanks for your reply. If I make a mst from the vendor MSI than I do not have the ISscript part.
And setup.exe /s/q/v"transforms=filename.mst /qn l*v %temp%/filename.log" doest not always work.
With kind regards... Willem
Thanks for your reply. If I make a mst from the vendor MSI than I do not have the ISscript part.
And setup.exe /s/q/v"transforms=filename.mst /qn l*v %temp%/filename.log" doest not always work.
With kind regards... Willem
Posted by:
TomB
18 years ago
Have you tried:
Setup.exe /s /v"/qn \"TRANSFORMS=path\filename.mst\" l*v %temp%/filename.log"
The \" will allow you to put " around the path to the transform incase there are spaces in the path or the file name.
I would suggest staying away from adding the install script in an MSI. What we do is just deploy the versions of InstallScript to our clients so they are availalbe for which ever applicaiton may need them. We acutally build our clients with these MSI files for ease of distribution.
Setup.exe /s /v"/qn \"TRANSFORMS=path\filename.mst\" l*v %temp%/filename.log"
The \" will allow you to put " around the path to the transform incase there are spaces in the path or the file name.
I would suggest staying away from adding the install script in an MSI. What we do is just deploy the versions of InstallScript to our clients so they are availalbe for which ever applicaiton may need them. We acutally build our clients with these MSI files for ease of distribution.
Posted by:
WillemJan
18 years ago
Hello TomB,
I'll give it a try, I have not already done so.
With kind regards... Willem
I'll give it a try, I have not already done so.
With kind regards... Willem
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.