Interesting and I believe I saw it before:
set the feature level to 0 if InstallMode is Typical. It installs
the remaining feature (those with level 1); an upgrade later
and all features are installed.
But if I do an InstallMode Custom, and select the features from the
SelectionTree, th
Just found it - it's MsiQueryFeatureState. The good thing is that it
accepts a product code which
I can retrieve with MsiGetProperty(.., "EXISTINGPRODUCTS" ...
Next, I should construct an ADDLOCAL string which concatenates the features.
Best regards,
Calin
PS.
it still feels like a work
Hi List,
I am running an upgrade dialog and from the log I see that
MigrateFeatureStates correctly detects the feature which was previosly
installed. However, an upgrade will install not only that feature, but
also the rest of the features. The tutorial from tramontana.hu upgrades
based o
3 matches
Mail list logo
