[wix-users] How does pyro find the files?

[Bob Arnson]

It does, but yes, it takes the simple approach: Extract files out of the .msi and update the .wixpdb to point to the extracted files.

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Blair Murri via wix-users
Sent: Monday, 11 February, 2019 20:18
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>; Hoover, Jacob <jacob.hoover at greenheck.com>
Cc: Blair Murri <osito at live.com>
Subject: Re: [wix-users] How does pyro find the files?

It might. My interest was avoiding build slowdowns caused by yet another wholesale copying of several hundred MB of files.

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Hoover, Jacob <Jacob.Hoover at greenheck.com>
Sent: Monday, February 11, 2019 10:55:33 AM
To: WiX Toolset Users Mailing List
Cc: Blair Murri
Subject: RE: How does pyro find the files?

Blair,
  Doesn't melt do the rerooting?

"%WIX%\bin\melt" RTM\Foo.msi -out RTM\CorrectedFoo.wixpdb -pdb RTM\Foo.wixpdb -x Temp\RTM


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Blair Murri via wix-users
Sent: Saturday, February 9, 2019 2:24 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Blair Murri <osito at live.com>
Subject: Re: [wix-users] How does pyro find the files?

Simple patches (that patch all changed parts of the product) don't need content in the PatchFamily element(s).

But first, you should test (in a VM you rollback) that you can successfully apply using the MSI command-line for a small update the update MSI over an installation done with the first MSI. If that doesn't work, no patch ever will (and you will need to go through the compound rules and figure out what you need to fix).

Second, make sure that the two wixpdbs were not built into the same output directories, and that the source files from each of the two builds are still available. If you simply built the two versions one-after-the-other, saving off the wixpdb from the first build, then when torch grabs the files indicated in the first wixpdb and finds the second packages files at the path, it will compare them to the same file (from the second pdb) and conclude that there were no differences between the files (and thus the patch will not contain any differences to apply).

The one tool I wanted to add for patching was one that rerooted a wixpdb file (to allow pulling a previous build output into an alternate location) but I never had the opportunity to make it generic.

Blair

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Reuss, Matthias via wix-users <wix-users at lists.wixtoolset.org>
Sent: Friday, February 8, 2019 6:39:24 AM
To: WiX Toolset Users Mailing List
Cc: Reuss, Matthias
Subject: [wix-users] How does pyro find the files?

Hi there,

Again concerning patch creation (be it worth it or not...)

So far, we have created patches using PCP files. Now we try to evaluate the "Pyro way" of creating patches.

When creating a patch following the sample from the documentation http://wixtoolset.org/documentation/manual/v3/patching/wix_patching.html, and the resulting .msp is *very* small.
It turned out that there are no files inside.

After investigating a bit, I wonder where pyro is supposed to get the files from.
The <Patch> element and its children do not contain file information, in contrast to the <Family> element used in PCP creation.
Neither does the .wixmst created by torch, nor does the pyro command line.

So how does pyro know which filesets to consider, which upgraded files to include, etc.?

Best regards

Matthias Reuss

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

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
NOTE: This email was received from an external source. Please use caution when opening links or attachments in the message.

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