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
- :
- more info
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 15, 2007
02:32 PM
Costing, InstallLevel, and sequencing
I have a basic MSI project wherein we use information entered in the Customer Information dialog to determine what features should be exposed to the user.
The catch-22 is as follows:
In my current implementation, the "Next" button of the Customer Information dialog (1) Validates the input fields and sets a property upon which all feature conditions depend. (2) If the input is valid calls (2a) fileCost, and (2b) CostFinalize. (3) Goes to next dialog.
This properly recalculates Feature conditions, and features are properly displayed when they are supposed to be, but file costs are not displayed. Instead the string "Compiling cost for this feature..." is dispalyed.
Has anybody doene something similar? Any suggestions?
The catch-22 is as follows:
In order to properly activate Features in the Selection Tree, CostFinalize must be called after the Customer Information Dialog to recalculate Feature Conditions.
In order to properly show feature costs in the Custom Setup Dialog CostFinalize must be called before the Dialog Sequence containling the SelectionTree begins.
In order to properly show feature costs in the Custom Setup Dialog CostFinalize must be called before the Dialog Sequence containling the SelectionTree begins.
In my current implementation, the "Next" button of the Customer Information dialog (1) Validates the input fields and sets a property upon which all feature conditions depend. (2) If the input is valid calls (2a) fileCost, and (2b) CostFinalize. (3) Goes to next dialog.
This properly recalculates Feature conditions, and features are properly displayed when they are supposed to be, but file costs are not displayed. Instead the string "Compiling cost for this feature..." is dispalyed.
Has anybody doene something similar? Any suggestions?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 01, 2007
02:48 PM
I should point out that this problem only exists in Vista. The costing behavior works fine in XP.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)