Well add my name to this request as well to having this work be put to the
top of the list
Since Purely WiX patching requires generation of the .wixpdb files I would
like to know how these work if the install supports multiple languages? We
had generation of the .wixpdb files turned off as at
.net
> Date: Sun, 10 Nov 2013 00:40:53 +
> Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
>
> Blair, this sounds really promising! Are there any examples of this that
> you can share?
>
> Stephen Tunney
> Nuance Communications, Inc.
> Solutions
)
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: November-09-13 2:09 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
For whole file patching, you need to write a BinderFileManager and put it into
an extension
ndline
options. That would solve the issue for your build, and you won't have to enter
the quagmire of IgnoreRange.
> From: stephen.tun...@nuance.com
> To: wix-users@lists.sourceforge.net
> Date: Fri, 8 Nov 2013 18:26:11 +0000
> Subject: Re: [WiX-users] Purely WiX patching and Fe
essage-
From: John Cooper
Sent: Friday, November 8, 2013 3:59 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Learn something new every day. Gave -delta a spin and it seems good. I'll
have to give it a spin without PatchFa
59 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Learn something new every day. Gave -delta a spin and it seems good. I'll
have to give it a spin without PatchFamily next and compare results.
--
John Merryweather Cooper
Bui
: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Friday, November 8, 2013 1:59 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Learn something new every day. Gave -delta a spin and it seems good. I'll
have to give it a spin wi
-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Friday, November 8, 2013 3:30 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Is this
riday, November 8, 2013 1:04 PM
To: [hidden email]
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Well I just did a test of Patch Creation using two different builds of our next
release of our software, which the .msi files are 118 MB in size, and if I set
the WholeFilesOnly="yes&
Is this: pyro -delta ?
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Friday, November 8, 2013 1:04 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Well I just did a test of Patch Creation using two different
Well I just did a test of Patch Creation using two different builds of our
next release of our software, which the .msi files are 118 MB in size, and
if I set the WholeFilesOnly="yes" the patch .msp size is 20MB. Now if I set
the WholeFilesOnly="no" then the size of the .msp is only 3.8 MB. Way
sma
e WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
The latter. Binary diffs are non-trivial. For example of this, see how TFS
handles binary check-ins. Like you, my builds version every rebuilt assembly
every build. So, we're guaranteed at least several dozen "
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Friday, November 8, 2013 1:16 PM
To: wix-users@lists.sourceforge.net
Subject
Okay Rob, taking out the PatchFamily does allow the patch to all updated
files to be correctly patched and therefore does reduce the complexity of
this method...
Now if we look at Stephen's issue I can see this being a major concern as we
also do the same thing where files are updated with version
Hey Stephen,
Here is the contents for my sample build.bat file:
@echo call melt.exe to fix the Version 1.0 wixpdb file so that we do not
have to worry about original source files/folders.
Melt.exe Ver1.0\product.msi -out Ver1.0Corrected\product.wixpdb -pdb
Ver1.0\product.wixpdb -x Ver1.0Corrected
[WiX-users] Purely WiX patching and FeatureRef
I guess I that is what I get from following documentation examples like what is
in the current Wix Toolset documentation:
http://wixtoolset.org/documentation/manual/v3/patching/wix_patching.html
Okay Rob I'll relook at my samples, make the modifica
]
Sent: November-08-13 12:49 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
I'm always a bit behind on patching stuff but it sounds like your adding
PatchFamilies and that kicks in filtering. Filtering is designed to provide
very
November-08-13 12:37 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Okay I have done a bit more testing with Pure Wix and Melt and here is what I
have found with my testing.
Create Product.wxs with a bunch of components in root and I also cre
I guess I that is what I get from following documentation examples like what
is in the current Wix Toolset documentation:
http://wixtoolset.org/documentation/manual/v3/patching/wix_patching.html
Okay Rob I'll relook at my samples, make the modifications, and start my
patch testing again to verify
don't add PatchFamilies.
Then the filtering pulls in everything that changed... like PCP does (IIRC).
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Friday, November 8, 2013 9:37 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Purely WiX patching
Okay I have done a bit more testing with Pure Wix and Melt and here is what I
have found with my testing.
Create Product.wxs with a bunch of components in root and I also create a
fragment with is bunch more components.
I then built this msi and associated .wixpdb file.
I then updated some of th
> On 28-Oct-13 22:05, Tunney, Stephen wrote:
>> Ok, good to know. I have thousands of components though spread across a
>> dozen features. Those features are shared amongst 8 products :)
Stephen, how did you make out with your patch creation using this Pure-Wix
method?
We are just looking into
12:51 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Hey Bob,
Thank you for your feedback, perhaps you could assist me with my problem then.
It appears as though my work with Melt and Torch is ignoring me :(
Here is a link to the
]
Sent: October-29-13 12:51 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
Hey Bob,
Thank you for your feedback, perhaps you could assist me with my problem then.
It appears as though my work with Melt and Torch is ignoring me :(
Here
ttach the wixmst and wixpdbs if you'd like.
Stephen
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: October-28-13 11:18 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
I would choose "none of the above.&
or a feature on the fly
>
> Bob, do you have any insight into what my next move should be? This is a
> very complicated set of products.
>
> Thanks for everything so far! WiX rocks!! :)
>
> -Original Message-
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent:
users@lists.sourceforge.net
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
On 28-Oct-13 20:38, Tunney, Stephen wrote:
> Adding DirectoryRef to the same boat as FeatureRef. I've added all
> directoryRefs, including the one that includes the component that I
> know has been u
On 28-Oct-13 20:38, Tunney, Stephen wrote:
> Adding DirectoryRef to the same boat as FeatureRef. I've added all
> directoryRefs, including the one that includes the component that I know has
> been updated and still no dice. :(
When used in patch family filtering, only a ComponentRef will includ
PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Purely WiX patching and FeatureRef
Hello again everyone,
Ok, so I've finally managed to get a patch generated. Good for me, I get a
gold star :)
Now I have a few questions
1) It looks as through using
Hello again everyone,
Ok, so I've finally managed to get a patch generated. Good for me, I get a
gold star :)
Now I have a few questions
1) It looks as through using FeatureRef in my PatchFamily doesn't work.
The result is an empty CAB file and a pyro.exe error PYRO0227
2) If I s
30 matches
Mail list logo
