I'm using heat to try and harvest a directory of all the pdb files. I know that
there is an option for heat to look into the vcproj files to get them, but I
may need to expand this in the future to deal with other file types as well,
such as linker map files, and the like.
What I've got so far
There are no bugs currently open on torch/pyro so there are no planned
updates.
Please open bugs and be as specific as possible about the issue. Patching
issues can be particularly difficult to reproduce if complete detail is not
provided.
On Thu, Aug 2, 2012 at 11:40 AM, Jeanne Dixon wrote:
>
Going back to the old patch creation method worked!
I followed the example in the link but I had to make a few changes (some of the
properties were old).
Here is my new wxs patch file:
http://schemas.microsoft.com/wix/2006/wi";>
http://www.mywebsite.com/";
Cl
I cannot suggest a solution for the patch problem you currently have, but I
might be able to suggest an alternative. I was unable to use the pure WiX
patching technique, as I was attempting to patch a file in a merge module.
The WiX help describes two methods of patch generation, the first WiX only
I could never get the new patch building mechanism
(http://wix.sourceforge.net/manual-wix3/wix_patching.htm) to work, so I fell
back to the older patch creation method.
(http://wix.sourceforge.net/manual-wix3/patch_building.htm) For what it's
worth, the wixpdb files are XML files. From what I
You would need to author your install to remember it, see this post
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Property-pattern
Neil
-Original Message-
From: Uma Harano [mailto:uhar...@esri.com]
Sent: 02 August 2012 16:53
To: General discussion for Windows Ins
Hi
I need some confirmation on what I should do about setting the installation
folder during maintenance mode.
When the first time install sets the install location to non default location,
does the msi remember this for subsequent maintenance operations? Or should I
create a custom action d
This is getting really frustrating...
I followed the instructions to make an administrative install for both the
original and updated versions. I reran torch (using the msi files instead of
wixpdb) and pyro built the patch without errors. However, the patch is still
not including the changed fi
An administrative installation is created using your built MSI. It's a bit
like extracting files from a zip.
Msiexec /a TARGETDIR=
This thread on admin install patching may help
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Minor-upgrade-o
r-Patch-creating-using-Visual-Studio-2010
I have messed about with the patch some and while I got rid of the pyro error I
still get a warning about the cab files being empty and the patch created
basically contains nothing (when I look at it in Orca all I see is the version
number has changed; no files are listed at all).
I have been s
I have tried that and it did not help. PDF files do not have version numbers.
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: Thursday, August 02, 2012 5:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Assistance with creating a pa
You should change version of the file which is included in the patch.
-Original Message-
From: Jeanne Dixon [mailto:jdi...@cots.com]
Sent: Wednesday, August 01, 2012 7:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assistance with creating a patch
12 matches
Mail list logo
