Call install through .MSI
I'm having an issue with calling an installer through a .MSI. Here is the situation. I have a package which is an installshield .exe. The .exe has 3-4 .msi's within it. There is also a patch via installshield .exe which has 1 .msi within it. When the installshield .exe runs, it extracts the 4 .msi's and installs.
I want to create a custom action to run the installshield .exe silently then proceed to the patch. I've tried inserting this custom action in various parts of the install sequence but can't get it to complete.
Does anyone have any experience with this? I've never done this before.
Thanks
Answers (5)
What have you tried to run the main .EXE silently?
You can try running setup.exe /r to create a record file called setup.iss in the C:\Windows directory. You can than copy this file to the source directory (\\fileshare\App) and run the setup.exe /quiet /f1"\\fileshare\App\Mysetup.iss"
http://helpnet.installshield.com/installshield18helplib/IHelpSetup_EXECmdLine.htm
Nested MSIs are A Really Bad Idea. I would use the MSIs that the EXE extracts and create transforms for each of them. Your deployment system can then be used to, er, deploy them.
Comments:
-
Ha! You haven't seen our deployment system! We deploy stuff with batch files and logon scripts.
I think what you've mentioned is probably the way to go though. I'll take this approach, thanks. - Secondlaw 12 years ago
>It can delete certain things unknowingly
Huh? Piffle! The MSI/MST combination is under your control!!!!!
It is not recommended to repackage/extract MSI and create transform for Installshield created MSI. We have faced problems earlier with this. It can delete certain things unknowingly. It is recommended to create an .iss file for install and uninstall.
Yeah, not sure what he means by "It can delete certain things unknowingly".
If the .exe /r works (sometimes it doesn't) Give that a shot. Or else I would got he MSI/MST route.
