Hi,
- Wix based on Windows installation technology(msi), which is
controlled/managed by windows installer service.
- Its Microsoft recommended installer building software which has built
in support in windows. NSIS is not more than a wrapper over scripting
language where as WIX/MSI is specifica
Hmm,
Just a guess but...
InstallCommand="/s /v"REBOOT=ReallySupress /qn /l*v
[LogPathVariable]""
And then if it fails, what does the bundle log show when it executes your
ExePackage? What is the error code that is returned? It should log all the
options passed to the package so we could tra
If I run from cmd the ExePackage in silent mode, and suppress reboot, with this
command line parameters it works"/s /v"REBOOT=ReallySupress /qn /l*v
%temp%\MyExe.log""
but if I use this InstallCommand in the ExePackage the package return an error
and doesn't installInstallCommand="/s /v"REBOOT=
Exe package logging would be dictated by the Exe. You could try passing /? To
the exe to see what parameters it supports. From there, you can customize the
parameters the bundle passes to the package to get the desired result.
-Original Message-
From: Marco Tognacci [mailto:mark...@li
Is this a bug in wix, or this is not the right way for enabling log for
ExePackage?I have tried to use LogPathVariable="MyExe.log" but the log doesn't
work.
> From: mark...@live.it
> To: wix-users@lists.sourceforge.net
> Date: Thu, 18 Apr 2013 20:09:29 +0200
> Subject: Re: [WiX-users] Wix ExePac
5 matches
Mail list logo
