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
- :
- MigrateFeatureStates doesn't work
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
‎Jan 06, 2009
09:15 PM
Major Upgrade in InstallShield
Hello,
as we know, Installshield provides Major Upgrade.
However, when I upgrade, I hope installer can remember the old features customer installed in the first time.
For Example:
At the first time, customer installed feature A,B,C;
when I do the upgrade,in the feature selection dialog, the feature A,B,C can be checked automatically.
Or any guy has other good ideas or solutions ?
Remember, this is not the modify, but upgrade.
Thanks in advance,
Honlory
as we know, Installshield provides Major Upgrade.
However, when I upgrade, I hope installer can remember the old features customer installed in the first time.
For Example:
At the first time, customer installed feature A,B,C;
when I do the upgrade,in the feature selection dialog, the feature A,B,C can be checked automatically.
Or any guy has other good ideas or solutions ?
Remember, this is not the modify, but upgrade.
Thanks in advance,
Honlory
(9) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 06, 2009
09:38 PM
You don't say, but since you use the term "Major Upgrade", I'm assuming that you are working with an MSI Project.
Just for clarity, it's not InstallShield, but Windows Installer that provides the Major Upgrade catabiltiy (InstallShield does make it very easy to populate the proper tables through its GUI).
The MigrateFeatureStates standard action does what you're looking for. The MSI Help Topic "MigrateFeatureStates Action" describes this in detail.
Just for clarity, it's not InstallShield, but Windows Installer that provides the Major Upgrade catabiltiy (InstallShield does make it very easy to populate the proper tables through its GUI).
The MigrateFeatureStates standard action does what you're looking for. The MSI Help Topic "MigrateFeatureStates Action" describes this in detail.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 06, 2009
11:41 PM
Hello DanGalender,
Thanks for your suggestion.
However, I'm not clear that if I can set use "MsiSetFeatureState" in Major Upgrade ? How can I use it ? I did not find any configuration or settings in my ism project file.
Would you kindly provide more information for me ?
Thanks in advance,
Honlory
Thanks for your suggestion.
However, I'm not clear that if I can set use "MsiSetFeatureState" in Major Upgrade ? How can I use it ? I did not find any configuration or settings in my ism project file.
Would you kindly provide more information for me ?
Thanks in advance,
Honlory
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 06, 2009
11:57 PM
What I'm suggesting is that you don't have to do anything. The MigrateFeatureStates action which is already there will do what you're asking for.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 07, 2009
12:07 AM
But in fact, what does the Major Upgrade do is that uninstall first, and then do a new install. In the new install, in the feature selection dialog, the old selected features were not been selected.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 07, 2009
12:19 AM
The feature selection (and all dialogs) take place in the UI Sequence which occurs before the Execute Sequence (where the uninstallation of the earlier version takes place), so the earlier version is still installed when the dialog appears.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 27, 2009
11:30 AM
Hi...
I'm having a problem with this too.
It doesn't seem to remember the features that were selected.
To re-create :-
- create an empty Installscript MSI project.
- create four features, each with a component and 1 file.
- build the install.
- run the install, select 2 of the features and complete the install.
- set a new product code, package code & version no
- create the major upgrade entry to upgrade from the same upgrade code
- checked the MigrateFeatureStates feature was enabled for the upgrade
- built a new install
- 'upgraded' my first test install with the new install
- when choosing custom all the features are selected by default
Shouldn't this have remembered the features from the first install?
Regards,
Kevin Palmer
Orbis Software Ltd.
I'm having a problem with this too.
It doesn't seem to remember the features that were selected.
To re-create :-
- create an empty Installscript MSI project.
- create four features, each with a component and 1 file.
- build the install.
- run the install, select 2 of the features and complete the install.
- set a new product code, package code & version no
- create the major upgrade entry to upgrade from the same upgrade code
- checked the MigrateFeatureStates feature was enabled for the upgrade
- built a new install
- 'upgraded' my first test install with the new install
- when choosing custom all the features are selected by default
Shouldn't this have remembered the features from the first install?
Regards,
Kevin Palmer
Orbis Software Ltd.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2009
03:58 AM
i donno if it helps but: you can specify how the Update works.
In the Update Node you can select if you want to uninstall and reinstall which is default or detect differnces and install new files which is what you want
In the Update Node you can select if you want to uninstall and reinstall which is default or detect differnces and install new files which is what you want
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2009
10:17 AM
Jan.Eggers wrote:
In the Update Node you can select if you want to uninstall and reinstall which is default or detect differnces and install new files which is what you want
This is NOT the answer. That is about installer efficiency and frankly it is in my experience unworkable, always use Uninstall and Reinstall unless you are absolutely sure you know what you are doing and have total confidence that your developers are correctly versioning ALL files.
The problem in this thread should not be occuring by default. Something odd has been authored into your installer. This may be that you are changing the INSTALLDIR and it is doing a side by side install. Or that you have added conditions on the Features that override the MigrateFeatureStates?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2009
10:26 AM
Other possibilities are that you have set up the Major Upgrade entries incorrectly or that you have accidently spun the UpgradeCode instead of the ProductCode.
1. Check that the UpgradeCode is the same across both versions.
2. Check that the MajorUpgrade Item Advanced tab is set up as follows:
. Upgrade Code = {00000000-0000-0000-0000-000000000000}
. Minimum Version =
. Maximum Version = ***ALL_VERSIONS***
. Detect Only = No
. Migrate Feature States = Yes
1. Check that the UpgradeCode is the same across both versions.
2. Check that the MajorUpgrade Item Advanced tab is set up as follows:
. Upgrade Code = {00000000-0000-0000-0000-000000000000}
. Minimum Version =
. Maximum Version = ***ALL_VERSIONS***
. Detect Only = No
. Migrate Feature States = Yes