[wix-users] MSI patching question

[Bob Arnson]

Either fix your build so unchanged things are unchanged or tell WiX what changed. 

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Joel Budreau via wix-users
Sent: Tuesday, 15 September, 2020 19:14
To: Rob Mensching <rob at firegiant.com>
Cc: Joel Budreau <joel.budreau at gmail.com>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] MSI patching question

Ideally, would a patch creation process be automated simply by diffing the two MSIs? Or in practice, does the developer really need to know what’s changed and author the patch.wxs file afresh each time (referencing the necessary components as ComponentRef’s)?

- Joel

> On Sep 15, 2020, at 3:58 PM, Rob Mensching <rob at firegiant.com> wrote:
> 
> It's complicated. Starts with PatchFamily/ComponentRef
> 
> ---
> Short replies here. Complete answers here: https://www.firegiant.com/services/
> 
> -----Original Message-----
> From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Joel Budreau via wix-users
> Sent: Tuesday, September 15, 2020 3:50 PM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Cc: Joel Budreau <joel.budreau at gmail.com>
> Subject: [wix-users] MSI patching question
> 
> Does anyone here create .msp patches?
> 
> Our build system re-builds and re-signs every file before packaging into the MSI. Because of this, when I take two MSIs (from two different builds) and attempt to make a patch between them, every file is included! How do people work around this??
> 
> Thanks,
> Joel
> 
> 
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/


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