then maybe check out messages from the
various file costing actions, where the files to be overwritten/removed
are determined and calculated.
Matt Weber
Computer Engineer
EmergingSoft(tm)
7900 Xerxes Avenue
Bloomington
,
however, this dialog should still appear if the user did indeed select
those IIS related features while not having IIS installed on the
machine.
I'm not worried about the integrity of the install, I'm just trying to
cover all the bases so first impressions are good with the new
install
but I see now that it applies to version 3 as well.
I replaced what I had before with a custom action that modifies the
value of SKIPCONFIGUREIIS based on the feature selection.
Works perfectly now! And, of course, Torch performs fine as well.
Thanks,
-Matt Weber
-Original Message-
This error will go away if I remove the above
.../> snippet I provided above.
Looking at the actual MSI tables, the entries in the CustomAction and
InstallExecuteSequence tables are equivalent between the two versions;
I'm not sure why they'd be picked up as a differe
4 matches
Mail list logo
