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
- :
- REINSTALLMODE "v" not used in IDE?
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
‎Oct 21, 2009
06:00 PM
REINSTALLMODE "v" not used in IDE?
Why is the default value of REINSTALLMODE "omus" when you create a new Patch Configuration, but the recommended value when executing msiexec on the command line "vomus?"
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2009
03:29 AM
The v is not required in a patch (.msp), only if you ship the update as a full .msi. And it has to be set outside the .msi file, on the command line. Setting REINSTALLMODE in property manager to include v would work.
Stefan Krueger
InstallSite.org
InstallSite.org
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2009
04:45 AM
Ok to explain clarify Stefan's comments a bit more....
Whenever you install an msi it caches the installation on your machine to be useful for uninstalls, reinstalls and repairs.
When you run a reinstall using just omus, it ignores the msi you provided it with and goes off to the cached version. specifying the v causes the msi to recache so it runs from your modified msi.
However an msp patch works slightly different. An msp is just a file containing changes and isn't a full msi. What it does is stream itself into the cached msi before running it. Therfore an msp cannot be cached itself but instead it updates the existing cache.
Hope this helps 🙂
Whenever you install an msi it caches the installation on your machine to be useful for uninstalls, reinstalls and repairs.
When you run a reinstall using just omus, it ignores the msi you provided it with and goes off to the cached version. specifying the v causes the msi to recache so it runs from your modified msi.
However an msp patch works slightly different. An msp is just a file containing changes and isn't a full msi. What it does is stream itself into the cached msi before running it. Therfore an msp cannot be cached itself but instead it updates the existing cache.
Hope this helps 🙂
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2009
08:14 AM
That's very helpful, and makes perfect sense. Thanks much.
Mark
Mark