Thanks for the fantastic detailed clarification on this issue! I will endeavour
to use the melt approach outlined in Bob's post.
-Nick
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET i
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Thursday, January 8, 2015 8:02 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating pat
Sounds like undocumented functionality of Melt. I don't see anything about
using it that way in the WiX.chm.
Also, binder variable don't solve the problem of binding the source files
into the XML file. They only give you a way to list a bunch of paths to
probe. So they don't replace the functiona
Subject: Re: [WiX-users] Creating patches using wixout (-bf flag deprecated)
Bind paths vs. Visual Studio project references (e.g.
$(var.MyProject.TargetDir))...the latter doesn't require passing custom
parameters to light. Why make the specifying of a source file more arcane with
a bind
Bind paths vs. Visual Studio project references (e.g.
$(var.MyProject.TargetDir))...the latter doesn't require passing custom
parameters to light. Why make the specifying of a source file more arcane
with a bind paths binder variable? Especially when the use case is a patch
file in the unseen futur
t: Thursday, January 8, 2015 11:50 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Creating patches using wixout (-bf flag deprecated)
You need to start using the bindpath variables in your wxs sources. Melt will
take care of pointing the wixpdb
@lists.sourceforge.net
Subject: Re: [WiX-users] Creating patches using wixout (-bf flag deprecated)
Ouch. So now you have to keep your old and new source files on hand. Would be
nice to keep the bind-files option or work it into the wixpdb. Also, not being
able to bind the files into the wixout or
-users] Creating patches using wixout (-bf flag deprecated)
Ouch. So now you have to keep your old and new source files on hand. Would be
nice to keep the bind-files option or work it into the wixpdb. Also, not being
able to bind the files into the wixout or wixpdb means that if you move the
wixout
Ouch. So now you have to keep your old and new source files on hand. Would be
nice to keep the bind-files option or work it into the wixpdb. Also, not
being able to bind the files into the wixout or wixpdb means that if you
move the wixout/wixpdb and then try to run Pyro against it, all the paths
a
@lists.sourceforge.net
Subject: [WiX-users] Creating patches using wixout (-bf flag deprecated)
Hi All,
I am using light.exe to create .wixout files with the -bf flag, I now get a
warning saying that this flag is deprecated. I can't find information on why.
I'm using .wixout files with bundle binary data
Hi All,
I am using light.exe to create .wixout files with the -bf flag, I now get a
warning saying that this flag is deprecated. I can't find information on why.
I'm using .wixout files with bundle binary data to create patches (as described
in the Wix 3.6 book) and am now wondering if this is
Ah gotcha. Thanks :)
/Thomas
> -Original Message-
> From: Phil Wilson [mailto:phil.wil...@mvps.org]
> Sent: 22. maj 2013 19:57
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Creating patches
>
> If you want to s
tCode, MsiRunningElevated etc.
Phil
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: Tuesday, May 21, 2013 11:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating patches
Would you mind expanding on that? Because I don't know wha
Would you mind expanding on that? Because I don't know what you mean...
/Thomas
> -Original Message-
> From: Phil Wilson [mailto:phil.wil...@mvps.org]
> Sent: 21. maj 2013 18:58
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re
I think a check for the PATCH property is more typical.
Phil
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: Tuesday, May 21, 2013 6:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating patches
I was reviewing the
age-
> From: MrWiX [mailto:philipp.ew...@asamnet.de]
> Sent: 21. maj 2013 10:32
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Creating patches
>
> Identical file versions are definitely not the problem. (I just ran a test
> with
> WiX 3.7 and it work ju
o: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Creating patches
>
> Identical file versions are definitely not the problem. (I just ran a test
> with
> WiX 3.7 and it work just fine. Only got a warning that the patch contains to
> files.) It looks like your wixpdb
Identical file versions are definitely not the problem. (I just ran a test
with WiX 3.7 and it work just fine. Only got a warning that the patch
contains to files.)
It looks like your wixpdb files differ in more just the version number. Even
the referenced files are the same, the internal structur
No, I don't think so. Is that the cause?
/Thomas
> -Original Message-
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent: 19. maj 2013 17:08
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Creating patches
>
> On 13-May-13 02:47, Thomas D
On 13-May-13 02:47, Thomas Due wrote:
> I have built two versions of the installer, with the only real difference
> being the version nummer (1.2.0 and 1.2.5).
Did the versions of all the files change too?
--
sig://boB
http://joyofsetup.com/
Is no one able to help me?
/Thomas
> -Original Message-
> From: Thomas Due
> Sent: 13. maj 2013 08:48
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: RE: [WiX-users] Creating patches
>
> Hello,
>
> Yes I am using 3.7 for
. Also, make sure there are differences
between your target and upgrade.
I have a feeling that I have an ID mismatch somewhere, but I cannot figure out
where.
/Thomas
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 9. maj 2013 16:54
> To:
sage-
> > From: Thomas Due [mailto:t...@scanvaegt.dk]
> > Sent: 3. maj 2013 09:40
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Creating patches
> >
> > I have now modified my build script to use a locally b
aller XML toolset.
> Subject: Re: [WiX-users] Creating patches
>
> I have now modified my build script to use a locally build msi installer and
> comparing it with a version build on my build server yesterday.
> There is no practical difference between the two msi files except the versi
iginal Message-
> From: uni [mailto:unigauld...@gmail.com]
> Sent: 2. maj 2013 12:07
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Creating patches
>
> 于02 May 2013 17:31:10,Thomas Due写到:
> > Hello,
> >
> > I am trying to grasp
于02 May 2013 17:31:10,Thomas Due写到:
> Hello,
>
> I am trying to grasp the concept of minor and small upgrades, but I am having
> some trouble with getting it to work.
>
> First of all, it doesn't seem to work at all with 3.7.
> I have downgraded my WiX to 3.5, and there something happens at least,
I don't think the version number of a binary is taken into account when
analysing differences for byte-level patches. Try setting
WholeFilesOnly=yes (
http://wix.sourceforge.net/manual-wix3/wix_xsd_patchcreation.htm).
On 2 May 2013 10:31, Thomas Due wrote:
> Hello,
>
> I am trying to grasp the
Update:
I discovered that I had a wrong PatchBaseline Id, I fixed this so it is equal
to the installer, and got this error instead:
pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the
patch. Check to make sure the transforms you passed on the command line have a
ma
Hello,
I am trying to grasp the concept of minor and small upgrades, but I am having
some trouble with getting it to work.
First of all, it doesn't seem to work at all with 3.7.
I have downgraded my WiX to 3.5, and there something happens at least, but my
msp seems to be empty when I examine
Hello
I have WiX files that deploys features based on conditions. However I am having
trouble creating a patch (msp) for this WiX file, especially for files that are
deployed by conditional statements.
I am following the recommended process for creating msp.
1. Candle patch.wxs for crea
30 matches
Mail list logo
