You can use the MajorUpgrade element (use the UpgradeCode you prefer in your
Product element) and use just the offending UpgradeCode in the Upgrade element
(to find/remove versions using it).
> From: jacob.hoo...@greenheck.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 29 Jul 2013 17:57:43 +0000
> Subject: Re: [WiX-users] Multiple upgrade codes issue
>
> You might not be able to use the MajorUpgrade element (I haven't tested
> this), but if you author your Upgrade/UpgradeVersion elements to find and
> remove it you shouldn't have issues. The only down side is if they try to
> rerun the bad install after upgrading then that install won't be able to
> detect the new version.
>
> -----Original Message-----
> From: K Peters [mailto:kpet...@otaksoft.com]
> Sent: Monday, July 29, 2013 12:01 PM
> To: Wix Users List
> Subject: [WiX-users] Multiple upgrade codes issue
>
> Hi,
>
> I have taken over an install project created with Wise Install.
>
> The previous maintainers had accidentally created a second upgrade code for
> our main product and released the resulting MSI. Now we have one product out
> in the client base with two different upgrade codes. They then managed to
> hack? Wise to accept a second upgrade code and when I orca one of those MSIs
> I see both codes in the upgrade table.
>
> How do I correctly handle this in Wix going forward?
>
> Thanks for all help,
> Kai
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent caught
> up. So what steps can you take to put your SQL databases under version
> control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
