Feature Null instead of Absent
I have been having trouble with a Standard project removing files when a feature is deselected in Maintenance mode. I have created a test project that works right but I can not see the difference between it and my bad project. Anyway, I did some logging in both projects during the maintenance run and found a big difference:
Say I have Feature1 and Feature2 both installed. Then I run maintenance and deselect Feature1 so that all I should be left with on the machine is Feature2. Here are the relative lines in the logs of each project:
Feature1 Installed:Local Request:Absent Action:Absent
Feature2 Installed:Local Request:Null Action:Null
Feature1 Installed:Local Request:Null Action:Null
Feature2 Installed:Local Request:Local Action:Local
What could be going on in my installation to cause this?
I am using ISDev 7.02 Standard Project, everything compressed.
It turns out that I have conditions on every feature based on whether or not a property was 0 or 1. I needed to resolve them before CostInitialize. I have custom actions that set a properties based on various things. These properties are initialized to 0 but the CAs set them to 1.
It is strange that the features still showed up in the custom setup list on a modify run...