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 havin
>
>
>
>
>
> 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--
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
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
riginal 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
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
> bina
I can confirm this now that I produced two MSIs that don't have any
component rules problems. Some history of this problem can be found in
posts titled 'Does Pyro (or Torch) ignore 4-th version number?'.
I have 2 MSIs and 2 corresponding binary wixout files. Using new
patching with wixout input pr
7 matches
Mail list logo
