Turn Msi's back into exe file after customisations
Hello,
I have a vendor specific installshield ".exe" file that contains a .msi file and some .cab files.
When i run it it extract itself into %TEMP%, so i can there pickup the msi and necessarily cab files.
Now i have made some customisations to the msi file (delete some rows and set some defaults).
The question is: How can i turn back the .msi file including the necessarily .cab files into 1 single .exe file.
the same as original, but now including my own customisations. ( i definitly need 1 .exe file)
Is this possible with our installshield adminstudio?
I hope so!
I have a vendor specific installshield ".exe" file that contains a .msi file and some .cab files.
When i run it it extract itself into %TEMP%, so i can there pickup the msi and necessarily cab files.
Now i have made some customisations to the msi file (delete some rows and set some defaults).
The question is: How can i turn back the .msi file including the necessarily .cab files into 1 single .exe file.
the same as original, but now including my own customisations. ( i definitly need 1 .exe file)
Is this possible with our installshield adminstudio?
I hope so!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
cygan
13 years ago
go to the build menu and look for the release wizard
there is an option as you build the release to create a setup.exe
hope this helps but not sure why you don't want to use the msi and mst option
there is an option as you build the release to create a setup.exe
hope this helps but not sure why you don't want to use the msi and mst option
Posted by:
bsducky
13 years ago
Ok i will check the release wizard , and hope i can import all the original msi's/cab files into the exe file.
I can't use the msi and mst option, because it's for the end user that has to download the .exe file and doubleclick to install. and since i have to upload that to the vmware view broker website, it only can handle 1exe file, and i need to give it also the same name as original.
Maybe that explains it.
I can't use the msi and mst option, because it's for the end user that has to download the .exe file and doubleclick to install. and since i have to upload that to the vmware view broker website, it only can handle 1exe file, and i need to give it also the same name as original.
Maybe that explains it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.