#1295 DTF - Request for FeatureParent
Jason Ginchereau
01 August 2008 18:25
Interesting, I'd never noticed that FeatureParent automation property before. Unless I'm missing something, this looks like a rare case where the MSI automation interface exposes functionality that is NOT directly exposed by the Win32 APIs.
Still it is possible to get that information from the MsiEnumFeatures API. Currently DTF ignores the parent value returned by that API. So this is definitely fixable.
Can you log a bug on SourceForge for tracking? I should be able to resolve this within the next couple weeks.
-Jason-
Simon Powell
01 August 2008 09:51
its supported by the Installer Object of the Automation Interface.
Straight from the Windows Installer SDK...
"The FeatureParent property specifies the parent feature of a feature.
An empty string for this property indicates the feature has no parent and is a root item. This is a read-only property."
Why can't this be supported by the Installer object in DTF?
James Buddell
31 July 2008 13:33
I'm using DTF but cannot find an implementation of the Installer.FeatureParent property. I can work around this by opening a session on the product and querying the Feature table, but would rather not as starting the session is very slow and I am enumerating a number of apps.
I can see the info that I'm after under
HKCR\Installer\Features\<encrypted productcode="">, but with "-" preceding feature parents with installation state 2 (absent) - I assume other prefixes would be used for other feature states too but I have no advertised or run from source.</encrypted>
Just wondering if an implementation of the FeatureParent property is planned, or if anyone would recommend another way of exposing this data?
Discussion
FeatureParent property added in tomorrow's build.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 21 days (the time period specified by
the administrator of this Tracker).