View Full Version : CustomSetup doesn't preserve rules in Maintenance Mode!!

08-01-2008, 04:32 PM
I have several features that user can select in my CustomSetup dialog.
User can select different combinations based on some conditions.
Everything is fine when installing the first time.
But, once installed, I go to Add/Remove Programs -> Change -> Modify.
It looks like none of the rules are preserved.
In CustomSetup, if user deselects everything, then an error dialog pops up saying that features need to be selected.
But, in maintenance mode, even though I select features, I get that error dialog.
Does anyone have an idea why this might be happening???
Also, one of the rules in CustomSetup dialog is that when feature A is selected, feature C cannot be selected. (if user selects feature A and C together, user gets another error dialog saying that it can't be done)
But, in maintenance mode, I can select feature A and C together and the install goes on.
Any idea??

08-01-2008, 04:52 PM
Perhaps post examples of the conditions you're using?

08-02-2008, 09:04 AM
I've attached txt file that describes the conditions on CustomSetup when clicked "Next".
When in maintanance mode, I get "NothingSelected" dialog,
or it lets me do the first or second events without showing the "WronbCombError"...

08-04-2008, 12:47 PM
One thing to keep in mind is the the feature action (&) conditions test that the feature state is changing; if you want to test a feature's existing state, there are !feature=n conditions.

The MSI topic "Examples of Conditional Statement Syntax" has some samples.