Feature Tree vs MSI Features

[smcburney]

I've got an application being installed by a standard project. Its got a lot of features to it. The application itself is going to call MSI to load and unload some of the features.

However, when our app loads a feature that was previously unloaded, and later you go to the Maintenance setup, the feature is still marked as unloaded.

Is there any way to get the IS feature tree to match what MSI thinks? or is there a way to call in to IS to load the features instead of calling MSI?

I'm thinking I'll have to write a function that recursively parses out all the features, and call the MSI FeatureState function to get the state of the feature, then call FeatureSelectItem to update the feature states in IS7. Does this sound logical, or am I missing something?

[smcburney]

has no one else come up against this problem?

I wrote a function that recursively goes through all features setting their state in IS based on their state in MSI. Then I call this in OnMaintUIBefore. This seems to be a good solution, but are there any problems I'm going to encounter?

Does anyone at InstallShield actually read these messages?

I'm finding so many things in Developer 7 that are lacking or cannot be done. And everything I have read about developer 8 leads me to think it has all the same problems.