[wix-users] Bootstrapper and patching

[Patterson, Brent]

To clarify, this is not an issue about setting the correct bundle version.  That part is already handled.  What I'm trying to do is this:

I have two bootstrapper bundles, one for MSI and one for MSP.
Let's say the bundle for MSI is 2.0.0.0, and MSI is 2.0.0.0 as well.  The MSP is 2.1.0.0, and bundle for MSP is 2.1.0.0 as well.

I install the bundle with MSI, it adds the bundle entry to "Programs and Features", which shows it as 2.0.0.0
I then install the bundle with MSP, it correctly updates the install files, but "Programs and Features" still shows 2.0.0.0, and there's no "Installed Updates" entry for the bundle.

What I want to see is "2.1.0.0" in the Programs and Features.

How do I set up the bundles so this will happen?  Do they need to share same UpgradeCode GUID?  Or same Related Bundle GUID?  If using Related Bundle, which should I use? Patch, Upgrade, or Addon?  Or is this a feature that isn't implemented like Rob Mensching said?

Thanks again for your help!

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Hoover, Jacob
Sent: Thursday, August 4, 2016 11:06 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Bootstrapper and patching

Or you could supply the version to the patch from a MSBuild property.  That way your build script controls it, you can provide the same value to the MSI/Patch/Bundle, and it can easily be automated from your build server by supplying a Build number as a property.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Phill Hogland
Sent: Thursday, August 04, 2016 11:51 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Bootstrapper and patching

It seems like this could be achieved by inserting your tool (or an MSBuild ITask) into the BeforeBuild task of the bundle to get the MSI/MSP version and set a pre-processor variable in your .wixproj file (or write it out to a .wxi file), which is then used by your bundle project to set the version, so that candle has access to the desired version when you are compiling the bundle.

________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Rob Mensching <rob at firegiant.com>
Sent: Thursday, August 4, 2016 11:35:17 AM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Bootstrapper and patching

IIRC, there is a feature request for that. Maybe you could implement it?

_____________________________________________________________
 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 Patterson, Brent
Sent: Thursday, August 4, 2016 9:17 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Bootstrapper and patching

Yes.  I have a tool that builds both MSI/MSP and the bootstrapper bundle.  The tool replaces the version number, so they're always the same.  I.e. If MSI is 2.0.0.0, bundle is 2.0.0.0.  If MSP is 2.1.0.0, the patch bundle is 2.1.0.0.  But since the bundle hides the MSI, it shows the bundle's version number, and not the MSI/MSP's version.  I want to update the bundle's version number.

Thanks

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

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

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

________________________________

Xactware's opt-in mailing list allows you to receive Xactware News that is of interest to you. Visit my.xactware.com today to join or to update your email preferences!

________________________________

This email is intended solely for the recipient. It may contain privileged, proprietary or confidential information or material. If you are not the intended recipient, please delete this email and any attachments and notify the sender of the error.