Hi Alex
Thanks, this helps a lot!
Three follow-up questions (I'll go on to try-and-error that - but maybe you
know the answer straight away).
1. will UpdateVersion/ @MigrateFeatures="yes" schedule the
MigrateFeatureStates action automatically or do I need to manually schedule
in InstallExecuteSequence?
2. will MigrateFeatureStates also migrate the Feature/
@ConfigurableDirectory or do I need to add RegistrySearch plumbing?
3. ist there an easy way to convert your "PreventDowngrading" to a warning
(UI only) instead of an error/abort?
Many thanks again,
Mark
_____
Von: Alexander Shevchuk [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 9. März 2008 19:41
An: Markus Kuehni; wix-users@lists.sourceforge.net
Betreff: RE: [WiX-users] Always change the product code?
Hi Mark,
Major upgrade
(http://msdn2.microsoft.com/en-us/library/aa369786(VS.85).aspx) is the
easiest of upgrades to implement. The only downside, I can think of, is the
fact that it is a complete reinstall of the product, although by carefully
scheduling RemoveExistingProducts
(http://msdn2.microsoft.com/en-us/library/aa371197(VS.85).aspx) you can
minimize how many files will be deleted/copied during upgrade.
Here
(http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8
-major-upgrade.aspx) is my own understanding of how major upgrade can be
implemented. To make it work *in WiX*, you need:
- Change Product/@Id, Package/@Id, and Product/@Version
(incrementing the third field only is fine);
- Never change Product/@UpgradeCode;
- Make sure that Product/@Language is listed in Package/@Languages;
- Add records to Upgrade table;
- Schedule RemoveExistingProducts in the InstallExecuteSequence
table
I have not tried to remove downgrade prevention support, so you can play
with it to check if downgrade will be allowed. I dont see why it would not
since I had to go extra mile to prevent it.
Regards,
Alex
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Markus Kuehni
Sent: Sunday, March 09, 2008 8:36 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Always change the product code?
Hi
After having read about all the gotchas of minor upgrades, including the
necessity for msiexec command-line args, I think it's best (in our case) to
always change the product code and be sure to always get a clean install.
I expect it results in more file deleting/copying activity than would be
necessary, but that's ok.
Is there any other downside I should be aware of?
Can I still only change the third field of the product version number?
Is it true, that this way I can even perform a clean downgrade, if
necessary?
Is there a good example for <Upgrade> and <UpgradeVersion> ?
Thanks,
Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
