I have a weird problem with one of our installers: Previously we have had a web feature (lets call it "A") in our setup, which installs a larger amount of components. Internally, this feature consists of some components directly attached to "A", and it has two hidden sub features "A1" and "A2" with more components attached.
For the upcoming version of our product I have added a second web feature on the same level as "A" (e.g. "B"), which also installs some other components and shares some of the components with the feature "A". So, the user has the chance to decide, if he wants to install feature "A" or "B" or both.
Both features are child of a parent feature (this would be "C").
The weird problem I am faced with is: When the user selects during the installation, that all sub features of "C" are going to be installed, all files of feature "A1" and "A2" are missing on the target system (only "A" and "B" is installed).
If you modify the installation and remove all the features in "C" and finish the installation, then add feature "C" again - it works. If you leave out "A" and only add "B" on first time installation and later on add "A" during a modification it works also.
In the msi log file I see entries like this:
MSI (s) (10:34) [11:10:53:908]: Feature: A1; Installed: Absent; Request: Null; Action: Null
The hidden sub features are setup up like this:
To summarize my experience:
- First time installation of setup, with "C" and sub features: only "A" and "B" is installed, but "A1" and "A2" is missing
- Modify installation: remove "C" again - "C" including all A's and B is removed
- Modify installation: add "C" again: "C" is properly installed, including all A's and B
I am using AI12 for building the installer. I have attached two log files and feature name description in a zip file. From my point of view, Features "A", "A1" and "A2" have not being changed since the last version.
Thanks for your help!
Regards,
Roland