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
- :
- Re: Upgrade with new components
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
‎Sep 03, 2009
01:55 AM
Upgrade with new components
I an using Basic MSI Project.
In old version (1.0.1.0), I set the condition of a component to 0 so that the files in that components will not be installed.
In new version (1.0.2.0), I removed the condition of that component so that the files will be installed now.
However, when I upgrade from the old version to the new one, files in that component is not installed. It looks strange. Why?
I have another try. I didn't use condition, just added a component with files in new version. The new files cannot be installed through an upgrade, too.
Is there any explanation about this?
Thanks in advance.
In old version (1.0.1.0), I set the condition of a component to 0 so that the files in that components will not be installed.
In new version (1.0.2.0), I removed the condition of that component so that the files will be installed now.
However, when I upgrade from the old version to the new one, files in that component is not installed. It looks strange. Why?
I have another try. I didn't use condition, just added a component with files in new version. The new files cannot be installed through an upgrade, too.
Is there any explanation about this?
Thanks in advance.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 03, 2009
02:36 AM
When Using MSI the conditions do not work the next time you start the setup.
Therefore you can not use conditions to get this done.
Rebuild mij Basic MSI Installshield into a Installscript Installshield where I have more cotrol over this issue
Therefore you can not use conditions to get this done.
Rebuild mij Basic MSI Installshield into a Installscript Installshield where I have more cotrol over this issue
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 04, 2009
02:45 AM
Since the component hasn't been installed along with 1.0.1.0, I think it sort of make sense that it doesn't install while installing 1.0.2.0 as it has no target to upgrade. However it's weird that it still cannot be installed with adding a new component. We often add new components to our new release and the files can be installed correctly during the upgrade. Of course, it's different situation that the files don't exist in previous install. Not sure if the duplicate keypatch would cause something like this?
You can try to author the component as transitive component by setting the "Reevaluate Condition" to Yes. Hope it helps.
You can try to author the component as transitive component by setting the "Reevaluate Condition" to Yes. Hope it helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 09, 2009
09:43 PM
Or can I disable Upgrade feature? - That's to say, when user runs new version of package, call uninstaller of the old version automatically, or simply refuse to continue before he/she unsinstalling the old version.
Is this OK to implement?
Is this OK to implement?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 10, 2009
08:40 AM
In a minor upgrade, MigrateFeatureState action will ensure that previously installed components are upgraded, which is why the component with the condition change didn't get installed. You could fix that with a custom action that sets the ADDLOCAL property with the name of the changed component - see the help for more information.
When you add a new component, you can ensure it gets installed in a minor upgrade using the same method, or by marking it as required by another component that was installed, I believe.
Finally, a major upgrade (which automatically uninstalls the old version and then installs the new version) should also allow for the new component and the changed component to be installed.
When you add a new component, you can ensure it gets installed in a minor upgrade using the same method, or by marking it as required by another component that was installed, I believe.
Finally, a major upgrade (which automatically uninstalls the old version and then installs the new version) should also allow for the new component and the changed component to be installed.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)