[wix-users] WixStdBA supporting Upgrades

Hoover, Jacob Jacob.Hoover at greenheck.com
Tue Jun 21 13:28:42 PDT 2016


Too many assumptions, not enough facts.  The authoring would be a start, along with the underlying facts of what is changing in the upgrade. (From v1 to v2 of the bundle, is the exe package in question changing?)


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Rob Mensching
Sent: Tuesday, June 21, 2016 3:20 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WixStdBA supporting Upgrades

Yeah, use a DetectCondition that is unique per version. Otherwise it isn't really a DetectCondition for (only) that ExePackage.

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/ -----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Stephen Downard
Sent: Tuesday, June 21, 2016 1:12 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WixStdBA supporting Upgrades

I now understand my problem.   The DetectConditions are the same in both v1 and v2.  Does this mean that an upgrade Bundle cannot re-release (non-unique) an ExePackage as part of the upgrade Bundle? Therefore, the DetectConditions must be unique between releases?  This appears to be true.  

I must be able to re-release a required 3rd party installer as part of an upgraded Bundle.  Is there a way to tell the engine to uninstall v1 prior to installing v2?

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/


More information about the wix-users mailing list