This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Extract .msi from .exe (web media)
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 08, 2008
03:30 AM
Extract .msi from .exe (web media)
I need to specify previous version of MSI for current build. But I have a single .exe built. How can I extract .msi from .exe (in command line)?
(11) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 08, 2008
06:24 AM
The msi file itself will be decompressed to a temporary folder when you launch setup.exe.
Just launch it and look for a folder similar to this:
C:\Documents and Settings\\Local Settings\Temp\{SOME RANDOM GUID}
Modification time of the generated directory will help you locate the correct one....
Regards
Fred
Just launch it and look for a folder similar to this:
C:\Documents and Settings\
Modification time of the generated directory will help you locate the correct one....
Regards
Fred
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 08, 2008
07:03 AM
Yes, Fred, I know about where I can locate it, but I need to extract it without starting the installation. I need to do it in command line during automated builds.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2008
02:31 AM
No one has encountered a need in extracting .msi from .exe?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2008
03:06 AM
How about maintaining 2 builds, one compressed setup exe and one uncompressed cd image, and specifying the uncompressed previous version for both?
If i'm not mistaken, specifying the previous msi is only necessary when building patches, upgrade validation can be done from compressed images, right?
If i'm not mistaken, specifying the previous msi is only necessary when building patches, upgrade validation can be done from compressed images, right?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2008
06:49 AM
1. No two builds. There are a number of builds being done. They take time, plus running unit tests. More over we use source control. As a result I will need to create two IS setup projects that I will need to keep synchronized.
2. I am not sure about this. But I can say from what I came to is - yes, specifying previous version is needed when building patches. But I do not know if compressed images can be used for upgrade validation, because open dialog filter has only *.msi filter set up.
2. I am not sure about this. But I can say from what I came to is - yes, specifying previous version is needed when building patches. But I do not know if compressed images can be used for upgrade validation, because open dialog filter has only *.msi filter set up.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2008
03:56 PM
For validation you may use the compressed exe file, the drawback is that IS needs decopresses them to validate, so the whole process goes even slower.
At least in my GUI the the inputfilter is *.msi, *.exe when specifying upgradable versions.
At least in my GUI the the inputfilter is *.msi, *.exe when specifying upgradable versions.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2008
02:12 AM
Hello Fred,
I would like to clarify: do you mean that in "Release wizard" -> "Advanced settings" -> "Patch optimization (Optional)" section -> "Open dialog" to select "Previous package" you have filter for both .msi and .exe?
PS I ask, because in "Patch Design" view and in "Upgrades" view there is in fact filter for both .msi and .exe.
I would like to clarify: do you mean that in "Release wizard" -> "Advanced settings" -> "Patch optimization (Optional)" section -> "Open dialog" to select "Previous package" you have filter for both .msi and .exe?
PS I ask, because in "Patch Design" view and in "Upgrades" view there is in fact filter for both .msi and .exe.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2008
02:44 AM
I was referring to the "Upgrades" view.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2008
05:54 AM
I see. But I do it in "Release wizard" that differs from the way you describe. In there I have no .exe in filter. I tried to specify previous package manually so that it indicates to .exe and it argued:
ISDEV : warning -6620: Could not open the reference package '{path to .exe}' for key synchronization
It seems to be a dead lock...
ISDEV : warning -6620: Could not open the reference package '{path to .exe}' for key synchronization
It seems to be a dead lock...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2008
08:35 AM
Hi, I found the parametres for setup.exe documented here.
Perhaps the /extract_all parametre helps you out then?
Perhaps the /extract_all parametre helps you out then?
/extract_all:: Package's files should not be run but simply extracted (InstallScript and InstallScript MSI projects only)
Specifies that a self-extracting package's files should not be run but simply extracted to the location that is specified by.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 16, 2008
09:32 AM
Hi Fred,
My project is of Basic MSI type and it does not work with it - I have tried already.
My project is of Basic MSI type and it does not work with it - I have tried already.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)