Hi,
I am using Wix 3.6. I would like to create web installer using wix burn. I
saw the link for adding executable files in remote payload element and it
works.
Like this how can i specify for msi?. I need to create a web installer that
downloads msi and cab files from server and installs it in
You may be able to use some combination of MSIRMSHUTDOWN and
MSIRESTARTMANAGERCONTROL to get the result you want. Having said that,
you seem to be saying that MSI/RM is already scheduling a reboot if it
doesn't shut things down properly, but that seems to be the problem
you're trying to solve, so
Thank you for the pointers, Phil. I will give ReplacedInUseFiles a try.
I do see logs from RM saying that a reboot will be necessary. I am not sure if
a ScheduleReboot custom action needs to be defined with the proper conditions
for this reboot to happen. Currently, i do not have a
What was the exit code of that setup? I'd expect 3010 if it was going
to do a reboot. Did it reboot after the install that this log is from?
It's still not clear to me if it should be rebooting but isn't or not
rebooting but you think it should.
You shouldn't need a ScheduleReboot action if
I’m using version 3.8 of the WiX toolset integrated with Visual Studio 2012. My
WiX project is part of the same solution that contains my main project assembly
(and a dll built as a separate assembly). Everything worked fine with the
installer when I had the version numbers defined within my
The exit code seems to be 0.
Action ended 15:51:30: INSTALL. Return value 1.MSI (s) (60:04) [15:51:30:358]:
Note: 1: 1707 MSI (s) (60:04) [15:51:30:358]: Product: -- Installation
completed successfully.
MSI (s) (60:04) [15:51:30:358]: Windows Installer installed the product.
Product Name:
In wix38-binaries package, it seems that only the x86 platform version of
Burn.exe is provided (under wix38-binaries\x86 directory).
I am wondering if an ARM platform of Burn.exe would be provided too. If not,
are we allowed to compile one using the source code under wix38-debug\src\burn?
We'd love to build ARM as well but Microsoft didn't release all of the
tools/libraries to do so. Maybe you can get Microsoft to release the missing
ARM tools/libraries?
-Original Message-
From: Jun Yin [mailto:jun...@microsoft.com]
Sent: Monday, February 17, 2014 2:57 PM
To:
Off the top of my head, the VersionType in wix.xsd probably doesn't support
that syntax. Today. You could try suppressing schema validation on the compiler
and seeing if that avoids the problem.
-Original Message-
From: Grant Anderson [mailto:grant.ander...@dmcinfo.com]
Sent: Monday,
Hi,
I have ExecuteProgressActionDataText set in the bootstrapper:
Action: Time: ActionName Action Text
I would like to just show:
ActionName Action Text
Is it this code that is setting the Action: Time: in WIUTIL.cpp
case INSTALLMESSAGE_ACTIONDATA:
if (WIU_MSI_PROGRESS_INVALID !=
Hi all,
I have a RTM version of our software which has 2 client MSI’s
The Event Source on the RTM install is fine, all there, but on the upgrade
only 1 of the Event Source is showing up:
RTM:
PropertyRef Id=NETFRAMEWORK40FULLINSTALLROOTDIR/
PropertyRef Id=NETFRAMEWORK40FULLINSTALLROOTDIR64/
I'm not 100% certain on this, but I think the format of the message was
controlled by the MSI itself. If you don't provide a record, WI does some
default formatting for you. Instead of overriding the default or tweaking the
engine, have you tried to customize the message from within the MSI?
What are the conditions on the components? When do you have
RemoveExistingProducts scheduled? If you repair your upgrade, do the other
event sources show up?
-Original Message-
From: Steve-Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Monday, February 17, 2014 6:41 PM
To:
32 bit condition (sorry nabble removes the conditions :( hence I have put extra
spaces here...
Condition ! [ CDATA[NETFRAMEWORK40FULLINSTALLROOTDIR AND NOT VersionNT64] ]
/Condition
64 bit condition:
Condition ! [ CDATA[NETFRAMEWORK40FULLINSTALLROOTDIR64 AND VersionNT64] ]
/Condition
14 matches
Mail list logo
