On 10-08-19 1:10 PM, Wilson, Phil wrote: > ....and it might help to look at it in terms of a product line. Using two > products as an example: > > Prod1 v1.0 => Prod1 v2.0 => Prod1 => v3.0 > > And > > Prod2 v10.0 => Prod2 v11.0 => Prod2 => v12.0 > > Each of these is a product line where each new version is intended to replace > any already-installed pre-existing versions. Prod1 and Prod2 would each have > their own unique UpgradeId for the life of the product although each version > would have a new ProductCode. The point is that Windows makes it easy to do > the upgrades because all you do is use the Upgrade table to say which > previous versions you want to upgrade. You get the uninstall/upgrade for free > with RemoveExistingProducts. > > Phil Wilson
A corollary is if you want to install major versions side-by-side, you should use a different UpgradeCode for each major version, correct? -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
