Ok, that makes sense. However, I can't get it to work either way. The
problem is not in changing just the 4th version number either. I created
a simple C# console executable that has one line of code:
Console.Writeln("This is version 1.0.0.0");
and assembly info AssemblyVersion("1.0.0.0")] and
AssemblyFileVersion("1.0.0.0")].
I build WiX test project referencing this program with -bf -xo linker
options.
The output is WixTest1.msi but it is not msi file since it can't be
opened with Orca. Is it wixpdb or wixout? Torch doesn't like wixpdb
extension (error TRCH0048) but accepts wixout.
I then update console program by changing all the strings 1.0.0.0 above
to 1.0.1.0, then rebuild exe and WiX project, changing also Product
element, Version attribute to 1.0.1.0. This gives me the second wixout
file for input to torch and I get 31 KB large Diff.wixmst.
When I run Pyro it comes with PYRO0252 error meaning that it can't find
any transform.
Torch and Pyro invoking batch files content is the following:
"%WIX%bin\torch.exe" -p -xi -v -val g -val l -val r -val z
Version1000\WiXTest1000.wixout Version1010\WiXTest1010.wixout -out
Patch\Diff.Wixmst
"%WIX%bin\candle.exe" Patch.wxs
"%WIX%bin\light.exe" Patch.wixobj -out Patch\Patch.WixMsp
REM "%WIX%bin\pyro.exe" -delta Patch\Patch.WixMsp -out Patch\Patch.msp
-t RTM Patch\Diff.wixmst
"%WIX%bin\pyro.exe" Patch\Patch.WixMsp -out Patch\Patch.msp -t RTM
Patch\Diff.wixmst
Note above REMarked -delta option.
Patch.wxs content is:
<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>
<Patch AllowRemoval="yes" Classification="Update" Codepage="1252"
ClientPatchId="WiXTest1" Id="*" DisplayName="WiXTest1 Update"
Manufacturer="WiXTest1" MoreInfoURL="http://www.WiXTest1.com";
Description="Minor Update Patch" TargetProductName="WixTest1">
<Media Id="1000" Cabinet="Patch.cab" EmbedCab="yes"
Source="FIRSTPATCH_PROP">
<PatchBaseline Id="RTM"/>
</Media>
<PatchFamilyRef Id="WiXTest1_PatchFamily" />
</Patch>
<Fragment>
<PatchFamily Id="WiXTest1_PatchFamily" Version="1.0.0"
Supersede="no">
<ComponentRef Id="CONSOLEAPPLICATION1.EXE" />
</PatchFamily>
</Fragment>
</Wix>
Obviously, I am doing something horribly wrong in my adaptation of Peter
Marcu's blog example or there is a nasty bug somewhere in there.
-----Original Message-----
From: Blair Murri [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2008 1:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New wix binary delta patching doesn't work
The "-delta" switch of pyro builds on top of the whole-file patch
support in pyro, so if that isn't working, the delta addition won't do
anything to help you.
If you get pyro to build a whole file patch that updates your binaries,
then add the -delta switch and test the results.
________________________________________
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
