Instead of modifying the WiX source directly you might want to consider writing
your own heat extension, there is an example here:
http://neilsleightholm.blogspot.co.uk/2010/06/wix-reg-file-heat-extension.html
(I wrote is for WiX 3.0 but it should convert to 3.6 ok).
As you have a lot of files
I am new to WiX and am trying to use WixUI_Advanced and then replacing the
InstallScopeDlg with my own version (called InstallScopeDlgDsktp) which
includes a checkbox for adding a Desktop shortcut.
I attempt to do this by copying all the lines that reference the old
InstallScopeDlg in the WixUI_Ad
On 21-Jun-12 13:57, John H Bergman (XPedient) wrote:
> Yesterday, I updated to 3014, and not when I build inside Visual Studio I am
> receiving a whole bunch of ICE30 errors that look similar to this, it appears
> to be about one per project.
Do you get the same error when building from MSBuild o
On 20-Jun-12 11:23, David Watson wrote:
> after a rebuild some binaries that have unchanged code and version numbers
> are not byte by byte identical to the previous version. When I build a test
> patch with some of these binaries they are being included in the msp by the
> torch auto detection me
On 20-Jun-12 17:40, David L. Beckwith wrote:
> I like the button progress bar on installation. Shouldn't it also be used
> during repair and uninstall?
It is, at least on my machine with 3.6.3014.0.
--
sig://boB
http://joyofsetup.com/
--
On 23-Jun-12 20:28, Nick Ramirez wrote:
> Looking at the source code for the extension, that package has the
> DownloadUrl attribute but not the SourceFile attribute, so would that mean
> the user needs to have an internet connection?
Yes.
> Am I right in thinking that
> having a SourceFile attrib
On 22-Jun-12 10:20, Luca Bottari wrote:
> I succeded in the replacement but I don't know how to validate the second
> path in the BrowseDlg and in "Next" button.
That code is only designed to check the WIXUI_INSTALLDIR property.
--
sig://boB
http://joyofsetup.com/
between two wixpdbs?
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
If the files are not binary identical then WiX will think they need to
be patched (because they are different:).
Use PatchFamilies to explicitly control what is in the patch.
From: Da
I only get these errors inside visual studio, when I build outside, everything
builds fine.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Sunday, June 24, 2012 11:34 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Updating from V 3.6.2424.0 to Ver
Thanks, Bob!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-4-pre-req-in-WixNetFxExtension-tp7579058p7579070.html
Sent from the wix-users mailing list archive at Nabble.com.
--
I wish to mix 32bit driver and 64bit driver into same package, but the
problem is the two referenced library difxapp_x64 and difxapp_x85 can't be
imported into same package, otherwise, there is a error as below:
"Error 1 Duplicate symbol 'CustomAction:MsiProcessDrivers' found. This
typicall
11 matches
Mail list logo
