I have an installation that includes an optional Kernel Mode Driver. I have an install condition on the feature that will set the InstallLevel to 1 should the condition evaluate to true (default value is 101 or "do not install"). I modify this condition by changing the values of properties on the command line.
I can see this working on first installs however during a major upgrade, if I optionally choose to not install this KMD, the property is passed to the new installation but the KMD is still installed.
The condition is as follows:
MYPROPERTY <> 0 OR REMOVE="ALL"
I script this installation with a front end UI that handles all the user selections and generation of the command line. I launch my installer with a Reduced UI. In testing, I found that if I launch with a Basic UI setting (qb) that the behavior changes and the KMD will correctly get removed. My question is, why should the behavior change with only altering the UI level? I have a clear test case that shows this changes behavior but I would rather understand what is going on before I fix the bug and get it into the next release.
Thanks in advance.