Re: [WiX-users] migratefeaturestates

Found it, the inclusion range was not correct. -- View this message in context: http://n2.nabble.com/migratefeaturestates-tp4695528p4705376.html Sent from the wix-users mailing list archive at Nabble.com. -- Download I

[WiX-users] migratefeaturestates

I am trying to get the migratefeature state options working. I installed a first version of mu application and went through custom to set the features to non-default items Then ran my major upgrade, and chose custom, but the chosen features were not selected. I ran the verbose log, and it does s

Re: [WiX-users] MigrateFeatureStates vs MsiGetFeatureState

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

Re: [WiX-users] MigrateFeatureStates vs MsiGetFeatureState

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

[WiX-users] MigrateFeatureStates vs MsiGetFeatureState

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