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
- :
- Basic MSI to upgrade an Installscript MSI project
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
Jun 24, 2007
07:07 PM
Basic MSI to upgrade an Installscript MSI project
Hi All,
I've recreated our installer, which used to be an Installscript MSI project, as a basic MSI project. Im now having a problem in that when I run the new msi to upgrade an old installscript MSI installation, the new msi does not recognise the fact that the product is already installed. I want it to display the modify, repair or remove dialog when it is run, but it runs as if there was nothing installed.
I've copied the product and upgrade codes from the Installscript package into the msi, and even copied the package code as well. I know I have the right product code because after the second installation (with the basic msi), there is only one entry in the Add/Remove programs window, but the second install (which should actually be an upgrade/repair) still does not recognise the fact that the product code is already installed.
I did a quick search through the registry for the product code and noticed that after the Installscript MSI installation the product code was only found twice in the registry. After the basic MSI, the product code was all through the registry.
Is there a way to have the basic MSI recognise the fact that the Installscript MSI package is installed ?
Thanks,
Marcus
I've recreated our installer, which used to be an Installscript MSI project, as a basic MSI project. Im now having a problem in that when I run the new msi to upgrade an old installscript MSI installation, the new msi does not recognise the fact that the product is already installed. I want it to display the modify, repair or remove dialog when it is run, but it runs as if there was nothing installed.
I've copied the product and upgrade codes from the Installscript package into the msi, and even copied the package code as well. I know I have the right product code because after the second installation (with the basic msi), there is only one entry in the Add/Remove programs window, but the second install (which should actually be an upgrade/repair) still does not recognise the fact that the product code is already installed.
I did a quick search through the registry for the product code and noticed that after the Installscript MSI installation the product code was only found twice in the registry. After the basic MSI, the product code was all through the registry.
Is there a way to have the basic MSI recognise the fact that the Installscript MSI package is installed ?
Thanks,
Marcus
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 24, 2007
09:27 PM
After further investigation, it appears that the problem isnt actually a basic MSI / Installscript MSI issue, but may be to do with the version of InstallShield ?
The original installer was created with InstallShield 11 - the new installer that doesnt seem to recognise the old one is IS2008. Has anyone had similar issues to what I am having ?
I created an Installscript MSi and a basic MSI both with IS2008 and they know when each other are installed and try to upgrade each other, rather than doing a fresh install. That is why Im starting to think its an issue with the IS version.
Thanks,
Marcus
The original installer was created with InstallShield 11 - the new installer that doesnt seem to recognise the old one is IS2008. Has anyone had similar issues to what I am having ?
I created an Installscript MSi and a basic MSI both with IS2008 and they know when each other are installed and try to upgrade each other, rather than doing a fresh install. That is why Im starting to think its an issue with the IS version.
Thanks,
Marcus
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)