Create .mst from properties values
Hello all,
This is my first post here in appdeploy so bare with me! I´m also new to packaging but I have gone a one weeks course in AdminStudio so I have some clue how to package anyway.
I have a task to create a .mst file to a msi file and I also have documentation what properties you are suppose to use and what values to use, to send to the msi file.
I tried to create a .mst file in orca and simply change the values under "Properties". Some of the variables wasn´t present under "properties" so I created them. But the installation fails I´m afraid. Strange fault messeges about database files beeing corrupt I think.
So the question is: How would I best create a .mst file if I know what property variables and what values to use? I simply want a .mst file instead of using:
msiexec.exe /i "C:\XXXX.msi" value1=1111 value2=2222 etc... etc... /qb
I have access to AdminStudio btw.
Thanks for your help!
This is my first post here in appdeploy so bare with me! I´m also new to packaging but I have gone a one weeks course in AdminStudio so I have some clue how to package anyway.
I have a task to create a .mst file to a msi file and I also have documentation what properties you are suppose to use and what values to use, to send to the msi file.
I tried to create a .mst file in orca and simply change the values under "Properties". Some of the variables wasn´t present under "properties" so I created them. But the installation fails I´m afraid. Strange fault messeges about database files beeing corrupt I think.
So the question is: How would I best create a .mst file if I know what property variables and what values to use? I simply want a .mst file instead of using:
msiexec.exe /i "C:\XXXX.msi" value1=1111 value2=2222 etc... etc... /qb
I have access to AdminStudio btw.
Thanks for your help!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
pjgeutjens
13 years ago
hello,
First of all make sure the original MSI installs without transform, also make sure silent installs don't pose problems.
Now for the transform:
if you want to use Orca:
- open your original MSI
- select menu Transform->new transform
- make your changes in the property table (change values, make new properties)
- select menu Transform ->generate transform
- save your .mst
For adminstudio
- open your original msi
- make the necessary changes
- file ->save as -> choose filetype .mst
or you can make a response transform with Installshield, for this, on the startpage choose create new project -> transform and follow the wizard. at one point you'll get a checkbox to make a response transform. This will run to your setup's GUI and save the choices you make in an mst.
Hope this helps
PJ
First of all make sure the original MSI installs without transform, also make sure silent installs don't pose problems.
Now for the transform:
if you want to use Orca:
- open your original MSI
- select menu Transform->new transform
- make your changes in the property table (change values, make new properties)
- select menu Transform ->generate transform
- save your .mst
For adminstudio
- open your original msi
- make the necessary changes
- file ->save as -> choose filetype .mst
or you can make a response transform with Installshield, for this, on the startpage choose create new project -> transform and follow the wizard. at one point you'll get a checkbox to make a response transform. This will run to your setup's GUI and save the choices you make in an mst.
Hope this helps
PJ
Posted by:
anonymous_9363
13 years ago
This will run to your setup's GUI and save the choices you make in an mst.Pieter, whilst that is undoubtedly true, it won't, of course, create and set the properties which the OP requires. They will still need to be added afterwards.
Posted by:
pjgeutjens
13 years ago
Pieter, whilst that is undoubtedly true, it won't, of course, create and set the properties which the OP requires. They will still need to be added afterwards.
very true, just thought I'd mention it :)
EDIT: tbh personally I'm no fan of response transforms, I've seen loads of junk being pumped into my MSI's, or checkvalues on certain installed components that are machine specific.... like MDACInstalledVersion = <some number> and the like. Personally I consider them to be a good indicator, but that's about it
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
