Peter,
That worked perfectly =)
I thought I'd tried this at some point whilst debugging but clearly I
was mistaken...
Thanks,
Liam
On 30/04/2012 11:53, Peter Shirtcliffe wrote:
> It can be immediate if you schedule it after InstallFinalize.
>
> -Original Message
Hello,
I have a wix based installer that writes some registry values using the
standard wix registry element a bit like:
> Key="Software\Company\Key" Name="KeyName" Value="1"/>
Is it possible for me to be able to read these values from a *immediate*
custom action? If so when do I need to schedu
Unless I'm mistaken you'd need to create a different MSI for each
customer...
You could automate the process of building the MSIs via command line
scripts and use preprocessor / environment variables to have the build
process determine which logos, licence agreement and help / config files
to
Hello,
I have a custom action function written in C that is called from a Wix MSI.
This custom action runs successfully on Windows 7 (32-bit & 64-bit), Vista
(32-bit & 64-bit) and Windows XP 64-bit however appears to simply not run on
Windows XP 32-bit.
The underlying issue here was that co
-wix-.aspx
-Original Message-----
From: Liam Flanagan [mailto:l...@dyalog.com]
Sent: 16 February 2011 12:46
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching Using Purely Wix
Hello All,
I've been wondering if it's possible to create minor patches using the
Hello All,
Is there any way to view a wixmst file created via torch in the following
manner:
torch -xi -xo RTM.wixpdb QFE.wixpdb -out diff.wixmst
I was under the impression that the output file should be a xml; however I
appear to get a lot of excess at the top of the file which appears
Hello All,
I've been wondering if it's possible to create minor patches using the
"purely wix" method, however only using the baseline and QFE MSI packages
instead of requiring the original source files and structure that the MSIs
were built from. I want have the benefits of purely wix patching
I'm having some trouble creating a patch for a real world sized application
after having successfully followed the patching "using purely wix" guide
within the wix 3.x manual for a small test program.
The error is occurring at the final patch production phase (using Pyro) and
I'm getting the fo
8 matches
Mail list logo