You cannot check whether a condition or feature is going to be installed in a
feature or component condition, since costing hasn't taken place yet.
Maybe you have a very special use-case, but in most cases, you've likely got
your features badly organized. With more information, we may be able to
My software is basically a bundle of image file codecs (currently only two but
this may change in the future). The user should be able to select which of the
codecs should get installed. In addition, there should be an option to set if
the selected codecs should get registered in Windows
Components can also be included in more than one feature. Could you add
subfeatures under your codec features?
- Feature: “Core files” (required)
--- Subfeature: “Codec A” (optional)
-- Subfeature: “Windows Explorer integration” (optional)
--- Subfeature: “Codec B” (optional)
--
I forgot about it, but you may have to publish the AddLocal event. I guess
it's been a little while since I thought about it, because I can't remember
if you can add/remove features with a feature condition outside of the
feature tree or if you have to use the AddLocal event (published by the
Next
Hello,
is there a way to install a Component from a Feature A only if another Feature
B is to be installed too?
I came acrossthis comment
(http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditions/comment-page-1/#comment-7208)
and tried out the suggestion with a
5 matches
Mail list logo
