Re: [WiX-users] New wix binary delta patching doesn't work
I am using old-style patchwiz.dll patching with success on daily builds and I
haven't updated WIX for 4 months already.
Nevertheless, there are several reason to prefer new style delta patching so I
will let you know how it works with the latest WIX version as soon as I get
some extra iteration time.
Thanks for info!
-Original Message-
From: Heath Stewart [mailto:clubs...@gmail.com]
Sent: Friday, April 03, 2009 3:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New wix binary delta patching doesn't work
Are you still having the same problem with recent builds? A month or two ago
changes were made to fix a couple of issues with delta patching.
On Tue, Aug 19, 2008 at 5:57 AM, Tony Juricic wrote:
> 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:
>
>
> http://schemas.microsoft.com/wix/2006/wi";>
> ClientPatchId="WiXTest1" Id="*" DisplayName="WiXTest1 Update"
> Manufacturer="WiXTest1" MoreInfoURL="http://www.WiXTest1.com";
> Description="Minor Update Patch" TargetProductName="WixTest1">
> Source="FIRSTPATCH_PROP">
>
>
>
>
>
>
>
> Supersede="no">
>
>
>
>
>
>
> 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:bmu...@microsoft.com]
> 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
>
--
Heath Stewart
Deployment Technologies Team, Microsoft
http://blogs.msdn.com/heaths
TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD)
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE,
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and
subscription company, and TradeStation Europe Limited, a United Kingdom,
FSA-authorized introducing brokerage firm. None of these compa
Re: [WiX-users] New wix binary delta patching doesn't work
Are you still having the same problem with recent builds? A month or two ago
changes were made to fix a couple of issues with delta patching.
On Tue, Aug 19, 2008 at 5:57 AM, Tony Juricic wrote:
> 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:
>
>
> http://schemas.microsoft.com/wix/2006/wi";>
> ClientPatchId="WiXTest1" Id="*" DisplayName="WiXTest1 Update"
> Manufacturer="WiXTest1" MoreInfoURL="http://www.WiXTest1.com";
> Description="Minor Update Patch" TargetProductName="WixTest1">
> Source="FIRSTPATCH_PROP">
>
>
>
>
>
>
>
> Supersede="no">
>
>
>
>
>
>
> 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:bmu...@microsoft.com]
> 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
>
--
Heath Stewart
Deployment Technologies Team, Microsoft
http://blogs.msdn.com/heaths
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] New wix binary delta patching doesn't work
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:
http://schemas.microsoft.com/wix/2006/wi";>
http://www.WiXTest1.com";
Description="Minor Update Patch" TargetProductName="WixTest1">
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
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. From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Tony Juricic [EMAIL PROTECTED] Sent: Thursday, August 07, 2008 8:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New wix binary delta patching doesn't work Removing -delta option from Pyro's command line gives me the same result: it reports that no files are added to the patch cab. I'll need some time to try with changing the third version number since I'm doing tests on actual builds, not a toy system. I find it interesting that MSP built with Pyro is 3 MB large but patches only the database (where I believe only version and description strings have changed), while MsiMsp created 1.2 MB large MSP which does everything above but patches also the (updated) version resource in more than 50 Dlls and a few signed exes. -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2008 12:04 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New wix binary delta patching doesn't work Tony Juricic wrote: > I have 2 MSIs and 2 corresponding binary wixout files. Using new > patching with wixout input produced a msp file which applied > transformation to the original database (i.e. I could see that product > version was changed in ARP after patch application) but none of the > binary files were changed. In particular all updated exes and dlls had > new and larger version numbers and should have been patched too. > So does it work if you: 1. Use full-file patches? 2. Use delta patches but change the build (third) version number? -- sig://boB http://joyofsetup.com/ - 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 - 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
Re: [WiX-users] New wix binary delta patching doesn't work
Removing -delta option from Pyro's command line gives me the same result: it reports that no files are added to the patch cab. I'll need some time to try with changing the third version number since I'm doing tests on actual builds, not a toy system. I find it interesting that MSP built with Pyro is 3 MB large but patches only the database (where I believe only version and description strings have changed), while MsiMsp created 1.2 MB large MSP which does everything above but patches also the (updated) version resource in more than 50 Dlls and a few signed exes. -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2008 12:04 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New wix binary delta patching doesn't work Tony Juricic wrote: > I have 2 MSIs and 2 corresponding binary wixout files. Using new > patching with wixout input produced a msp file which applied > transformation to the original database (i.e. I could see that product > version was changed in ARP after patch application) but none of the > binary files were changed. In particular all updated exes and dlls had > new and larger version numbers and should have been patched too. > So does it work if you: 1. Use full-file patches? 2. Use delta patches but change the build (third) version number? -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] New wix binary delta patching doesn't work
Tony Juricic wrote: > I have 2 MSIs and 2 corresponding binary wixout files. Using new > patching with wixout input produced a msp file which applied > transformation to the original database (i.e. I could see that product > version was changed in ARP after patch application) but none of the > binary files were changed. In particular all updated exes and dlls had > new and larger version numbers and should have been patched too. > So does it work if you: 1. Use full-file patches? 2. Use delta patches but change the build (third) version number? -- sig://boB http://joyofsetup.com/ - 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
