Output while debugging candle.exe in Visual Studio
'candle.exe' (Managed (v4.0.30319)): Loaded
'C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll',
Symbols loaded.
'candle.exe' (Managed (v4.0.30319)): Loaded 'Z:\Wix\candle.exe'
'candle.exe' (Managed
I hit a similar problem and managed to fix it:
In the Process of the Build Definition, under advanced, change the MSBuild
Platform from *Auto* to *X86*. This forces the build to use the X86 version
of MSBuild, which in turn can run Heat.exe
Hope this fixes your problem.
--
View this message
Hey guys,
I've got a couple of custom actions set in InstallExecuteSequence that has no
conditions. I want these CAs to execute when modifying a feature to do some
backup and restore functionality.
The CAs run fine for normal install, patch install, feature uninstall etc.
However the CAs do
This was the first time I've ever run into this behavior. The most
frustrating part was that it was working for others on my team even though
they were using the same source. Later we discovered that checking the
code into and out of source control strips the streams.
On Wed, Feb 5, 2014 at
I now have this half-way working.
Installing on Windows 7 w/UAC succeeds
Installing on Windows XP fails
In .wxs:
InstallScope=perMachine
InstallPrivileges=elevated
CopyFile is setup in an immediate property and then executed deferred
without impersonation.
XP Install Log
On 04-Feb-14 07:40, Tony wrote:
votive install contains wixcomplusextension.dll and wixmsmqextension.dll
wix38-binaries contains retina.exe (and config)
That would be a bug. I think Complus was added for v3.9.
--
sig://boB
http://joyofsetup.com/
On 04-Feb-14 17:42, Martin Alley wrote:
I found the instructions in using this extension in a sample WiX setup
project a little confusing. I don’t get why the reference should be added as
a project reference
It shouldn't. There's nothing to hook up .csproj references as WiX
extensions. Use
My setup.exe / Bundle is blocked by our Symantec anti-virus. I have read the
previous postings on this issue from 2 years ago
(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reopen-Burn-triggers-virus-checker-ID-3431068-td7175855.html).
I guess the situation has not improved?
1. Sign your bundle.
2. Submit it to Symantec's false positive web page.
-Original Message-
From: Marty Offe [mailto:marty.o...@dh.com]
Sent: Thursday, February 6, 2014 4:30 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] setup.exe (Bundle) blocked by Symantec Endpoint
It knows about our custom actions as well and they rollback just fine.
On 02/06/2014 09:42 PM, David Connet wrote:
I have to wonder, why in the world are you using cmd.exe in a custom
action to copy a file? (**twitch** **twitch**)
CopyFile is much easier and msi knows about it (hence
I have to wonder, why in the world are you using cmd.exe in a custom
action to copy a file? (**twitch** **twitch**)
CopyFile is much easier and msi knows about it (hence handles
uninstall, rollback, upgrade, etc).
Dave
On 2/6/2014 5:35 PM, Gerry Reno wrote:
Ok, after some experiments:
The
Ok, after some experiments:
The copy file is like this:
CustomActionSchedule(Action=CopyFile,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData=cmd.exe
/c
copy C:\Program Files\OURCOMPANY\OURPRODUCT\OURFILE.exe
C:\OURSTUFF\[LogonUser]\ADIRECTORY\\)
And now since I added
12 matches
Mail list logo
