Hi.
On Thu, Oct 28, 2010 at 10:40 PM, Nick Ramirez wrote:
>
> You shouldn't need to schedule the MigrateFeatureStates action manually. The
> UpgradeVersion element has an attribute called MigrateFeatures that you can
> set to "yes".
Thanks a lot, that did the trick. My bad - I noticed that the f
You shouldn't need to schedule the MigrateFeatureStates action manually. The
UpgradeVersion element has an attribute called MigrateFeatures that you can
set to "yes".
As an example:
-
Learn WiX with the book:
https://www.packtpub.com/wix-a-developers-guide-to-windows-installer-xml
Hi.
I'm trying to support major updates for my application and it works fine so far.
Except for feature states.
I'm testing an update from version 1.9.0 to 1.9.1
ProductCode changes between MSIs (it's "*"/auto-generated for me)
Component GUIDs are stable for me (fixed)
1.9.0 and 1.9.1 have the s
3 matches
Mail list logo