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: Using MsiSetFeatureState problem
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 23, 2007
09:43 AM
Using MsiSetFeatureState problem
Hi
In my basic MSI setup I have a SetupType dialog in which the user choose the configuration ( Cleant, Server, WEB etc. )
Then according to the chosen configuration I use the MsiSetFeatureState to enable\diable features and show the all features in the CustomSetup dialog, ( I'm also trying to hide unneeded features but that's a diffetent story )
Than according to the choose of sub-features in the CustomSetup I'm using MsiSetFeatureState again to diable\enable sub-features
but it seems that the setup ignore this part and install all sub-features.
MsiSetFeatureState(hMSI,"N_CLIENT\\N_PD\\MicrostationInteg\\MICROSTATION_J",INSTALLSTATE_ABSENT);
Any idea what is the problem ?
In my basic MSI setup I have a SetupType dialog in which the user choose the configuration ( Cleant, Server, WEB etc. )
Then according to the chosen configuration I use the MsiSetFeatureState to enable\diable features and show the all features in the CustomSetup dialog, ( I'm also trying to hide unneeded features but that's a diffetent story )
Than according to the choose of sub-features in the CustomSetup I'm using MsiSetFeatureState again to diable\enable sub-features
but it seems that the setup ignore this part and install all sub-features.
MsiSetFeatureState(hMSI,"N_CLIENT\\N_PD\\MicrostationInteg\\MICROSTATION_J",INSTALLSTATE_ABSENT);
Any idea what is the problem ?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 29, 2007
03:18 PM
I think MsiSetFeatureState just wants the "leaf" feature name ("MICROSTATION_J") and not the whole subfeature tree; in MSI, internal feature names are unique, unlike features/subfeatures in InstallScript projects.
You might also be able to make use of Add and Remove control events, which might save you the trouble of creating custom actions...
You might also be able to make use of Add and Remove control events, which might save you the trouble of creating custom actions...