You cannot use the Message method to write to the install log when the custom
action is called using the DoAction control event. This is a limitation of
MSI.
--
View this message in context:
The base installer is in English. The other languages are embedded inside of
it. Based on your comments I am at a loss.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Monday, December 10, 2012 9:17 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
Could you provide the steps you're using to create the installer? With
command line arguments?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Falling-back-to-default-language-if-locale-is-not-present-tp7582282p7582309.html
Sent from the wix-users
MsiServiceConfig table contents:
MsiServiceConfigNameEvent ConfigType Argument
Component_
LPDS_Service.FA LPDS Service7 4 1
LPDSService.exe
MsiServiceConfigFailureActions table contents:
MsiServiceConfigFailureActions
Here is my log when my BA is downloading a msi package from a server:
(the bad thing is the overall progress percentage)
[1070:122C][2012-12-10T23:28:23]i338: Acquiring package: MySetup,
payload: MyPackage, download from: http://www.mydomain.lan/MyPackage.msi
I don't know why I cannot reproduce it, it seems ok now even with local
cache...
Maybe it was due to the fact that I was debugging the wixstdba.dll with
breakpoint on OnCacheAcquireProgress...
On Mon, Dec 10, 2012 at 11:36 PM, up2date.cyb...@gmail.com
up2date.cyb...@gmail.com wrote:
Here is my
I'm more of a .NET guy, where the session.Message method in the DTF library
can't be called from within a DoAction custom action. It calls the
MsiProcessMessage behind the scenes. So the Message method you're talking
about may be different.
It seems to be a part of something called the
7 matches
Mail list logo
