This would be considered a Major Upgrade. If the old MSI has a UpgradeCode property, you should strongly consider keeping that same as your UpgradeCode. In that case, simply code the Upgrade table (using the Upgrade and UpgradeVersion elements) as advised for major upgrades. I would recommend NOT setting the MigrateFeatures attribute since your features are structured differently.
Depending on your component layout (and if you keep the component guids/keypaths the same) you may be limited in where you place your RemoveExistingProducts action. It depends on how tight you are with the component rules. This list has several discussions on the placement for that action: feel free to search for those. If you are still confused at that point, feel free to ask for more help. The only reason you would need to generate your own custom action to detect the previous installer is if the previous installer didn't have an UpgradeCode property. Simple rules for all the IDs: PackageCode: If the MSI doesn't contain "exactly" the same content, change the guid. It is virtually always an error to have the Package/@Id value be anything except '*' in WiX v3 (I think it was all ?-marks in v2, but I don't recall). UpgradeCode: This code should generally NEVER be changed and should generally ALWAYS be included. The only time you muck with this one is when you are splitting/merging MSIs and that is both an advanced topic and a separate discussion. ProductCode: Change for "Major Upgrades", maintain same for servicing using patching. Anything else is advanced usage and it is too easy to mess up. If you never intend to patch, (you will ALWAYS - for the time being - release just MSIs) the most straightforward advice is to set this to '*' and let it autogenerate (it is the Product/@Id value). UpgradeCode, ProductLanguage, and ProductVersion taken altogether should generally point to a unique ProductCode. Because of that, we generally incorporate our build number somewhere in the ProductVersion value when building Major Upgrades. -----Original Message----- From: warne warne [mailto:warne...@hotmail.com] Sent: Friday, July 31, 2009 12:58 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] strategy for moving/migrating to WIX from other installer Hi, I have a new version of our product (version2) for which I created a new WIX 3.0 installer. The previous installer for version1 was created with an unknown old installer program. It is an msi though so I can open it in Orca to view product & upgrade Ids etc. I can also see that the features and feature components are structured different to what I have. These features are now not needed in the new WIX installer. Is this classed as a 'Major Upgrade' or Whats the general accepted strategy for moving to WIX installer in this situation? Im puzzled what to do in terms of productIDs, packageIDs and upgrade codes. Similar situation to this : http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg01097.html but wanted to make sure it was the right way to do it. If I have to remove the old version, is it possible to create a custom action in the new WIX installer to first detect old version is on the system and button below that to remove it? Just to make it elegant maybe.. thanks very much, _________________________________________________________________ Celebrate a decade of Messenger with free winks, emoticons, display pics, and more. http://clk.atdmt.com/UKM/go/157562755/direct/01/ ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
