Peter Marcu's Blog

PingBack from http://www.doctordeploy.com/blog/wix/wix-patching-something-you-didnt-build-with-wix-using-wix.html

It seems you need to provide -xo also when doing a diff on msi files. That makes the output format to be of wixout format which is implicitly done when using -xi.

At least that solved the same problem for me.

Your instructions don't match your example. You say;

"The difference here is that your patch authoring can be done using the WiX v3 Patch element and it follows the same workflow as patching a WiX v3 based msi after the first stage of creating the diffs."

Acording to your example referenced the first stage does not make the diffs it makes the .wxs.

1. Build Target Layout:

> candle.exe -dVersion=1.0 product.wxs

> light.exe -sval Product.wixobj -out 1.0\Product.msi

Another issue is you say;

"The command lines you need to run are all the same as the ones in my sample: Building a Patch using the new Patch Building System - Part 3. The only difference is that you need to pass the -ax command with a path to extract embedded binaries to instead of the -xi switch."

Below are the rest of your command lines and the only one that works is 3. Transform (torch.exe)

If you follow your instructions you get a diff.wixmst and that's it. None of your instructions explain how to do the next step after creating your diff file, which is 4. Building the Patch (candle.exe, light.exe,pyro.exe)

If we had better instructions we could do the last step of 4. which is pyro.exe

Can you please provide step by step instructions and assume you are talking to idiots because we don't know what you know :)

2. Build the Upgrade Layout:

> candle.exe -dVersion=1.1 product.wxs

> light.exe -sval Product.wixobj -out 1.1\Product.msi

3. Create the transform between your products:

> torch.exe -p -xi 1.0\Product.wixpdb 1.1\Product.wixpdb -out Patch\Diff.Wixmst

4. Build the Patch:

> candle.exe Patch.wxs

> light.exe Patch.wixobj -out Patch\Patch.WixMsp

> pyro.exe Patch\Patch.WixMsp -out Patch\Patch.msp -t RTM Patch\Diff.wixmst

hello, after some troubles regarding to use torch on MSI I have finally made a sample msp. I only wondered what does the

ComponentRef tag beyond <PatchFamily> element  in patch.wxs?

When entering a reference there, the patch file is really small instead when leaving it blank (none ref tags)???

Peter,

I have a 3rd party setup.exe which internally extracts am MSI and installs some setup. As MSI cannot be installed from inside an MSI, i want to create a merge-module for the setup.exe itself, coz the MSI that the setup.exe extracts has some other dependency file and hence the msi wouldnt run when clicked on it.

Is there any way to get msm for the setup.exe file?

Thanks

Patch.msp created and installed but it doesnot update the files. What might the issue? In the logs it has picked up the diff file Ids.

Referring to log of patch installation.

msiexec /update patch.msp REINSTALL=ALL REINSTALLMODE=amus /L*v patchinst.log

Files which differs are .aspx files and they are unversioned. Replace/overwrite existing unversioned (i.aspx) to unversioned (i.aspx)

just went through the child elements of patchfamily and added DirectoryRef instead of componentRef under patchfamily.  it works great now.

Problem while patch creation. They were some new directories/files and updated/removed files.

error PYRO0305 : Removing component 'com

_SERVICE_INSTALL_133' from feature 'WebService' is not supported.

pyro.exe : warning PYRO1110 : Component 'comp_SERVICE_INSTALL_121' was added to feature 'WebService'. If you can not guarantee that this feature will always be installed, you should consider adding new components to new top-level features to prevent prompts for source when installing this patch.

E:\Product\ReleaseManagement\webwiz\wxs\SuiteServices.wxs(202) : error PYRO0260 : Product '{11111111-1111-

1111-1111-111111111111}': Table 'CreateFolder' has a new row 'dir_SuiteService_Common_BPC_7/comp_SERVICE_I

NSTALL_117' added. This makes the patch not uninstallable.

at the last

pyro.exe : error PYRO0261 : This patch is not uninstallable. The 'Patch' element's attribute 'AllowRemoval' should be set to 'no'

it doesnot create patch.msp file..

pls suggest.

In patch.wxs i get this error even if i use to componentRef or DirectoryRef.

SuiteServices.wxs doesnot have components per file instead it has component groups.

When i set the attribute "AllowRemoval" to no. Then "pyro.exe : error PYRO0261 : This patch is not uninstallable" is gone.

BUT "error PYRO0305"  and "pyro.exe : warning PYRO1110 :" remains.

it doesnot create patch.msp file..

How do we patch a single file out of a component with multiple files in it? I noticed that you said one way is to generate the admin image so that bigger components can be broken into either smaller or individual components. Any link on how to do that? Thanks!

The problem I have is not about the changed files. They are being patched as expected. It is about the unchanged files in that component being included in the patch with the new version number as we can only point to a component instead of a file in the WXS file.

Marco,

Thanks for your efforts! I've been trying for many days to build a patch, unsuccessfully. The WIX user community doesn't seem to have any answers, but I've already found several things in this blog that should be in the documentation!

Here's what I have: I am using WiX 3.5.1030. I have 2 admin images of my product's versions 7.0.0 and 7.0.1. The original WIX instructions and documentation do not explain the -xi flag used with torch. I wasn't getting any errors from torch to lead me to believe that I should check the command line arguments, but I think even if I had, I might not have realized that I should use -a. Your reply to Chris says to use -ax, but I found I needed -a and to supply paths to the .MSI files (see complete command sequence below).

Question 1:

-pedantic doesn't seem to output anything - where would I find the messages?

Comment 1: Somewhere in this or the other Building a patch ... Part 3 blog, I found the answer to one of my questions that no one had answered. I think it's important to document that if you leave out all component refs, torch will check ALL components. All the examples use a single component, and therefore it's easy for them to add one ComponentRef. A real setup will have dozens, hundreds or (like mine) over a thousand components.

Question 2:

Quite a number of the changed or added components are in merge modules. If you leave the PatchFamily element empty, will torch look at all the components, even the ones added by a merge module?

Question 3:

Even though all of the above has resulted in a much larger .wixmst file (more likely to DO something), I am STILL getting the exact same PYRO0252 error from Pyro. I have tried dozens of combinations of naming of the Media Cabinet attribute (what IS this?), the PatchBaseline Id attribute, the PatchFamily Id attribute, etc. I think I've tried them all but it doesn't seem to matter. Here's the WSX:

<?xml version="1.0" encoding="utf-8"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">

 <Patch

   AllowRemoval='no' Manufacturer='Media Cybernetics, Inc.' MoreInfoURL='support.mediacy.com'

   DisplayName='Image-Pro Plus 7.0.1 Patch' Description='Patches an Image-Pro Plus 7.0 installation to 7.0.1'

   Classification='Update'>

   <Media Id='5000' Cabinet='RTM.cab'>

     <PatchBaseline Id='RTM' />

   </Media>

   <PatchFamilyRef Id="SamplePatchFamily"/>

 </Patch>

   <Fragment>    

       <PatchFamily Id='SamplePatchFamily' Version='7.0.0' Supersede='yes'>

       </PatchFamily>

   </Fragment>

</Wix>

and here's the command lines from my automated build's batch file:

"%WIX_DIR%\torch.exe" -p -notidy -pedantic -a IP7.0Target\ImageProPlus7.msi IP701\ImageProPlus701.msi -out IPP701Patch.wixmst > patchTorch.log

@if errorlevel 1 goto StopOnError

"%WIX_DIR%\candle" IPP701Patch.wsx > patchCandle.log

@if errorlevel 1 goto StopOnError

"%WIX_DIR%\light" IPP701Patch.wixobj > patchLight.log

@if errorlevel 1 goto StopOnError

"%WIX_DIR%\pyro.exe" IPP701Patch.wixmsp -out IPP701Patch.msp -t IPP701Patch IPP701Patch.wixmst > patchPyro.log

@if errorlevel 1 goto StopOnError

How can one troubleshoot the PYRO0252 error? Anything you can suggest would be great!

Thanks,

John