Blair,
1. I use the following syntax:
"$(WIX)Bin\torch.exe" -p -xi
"$(ProjectDir)Installers\Base\ProductSetup.wixpdb"
"$(ProjectDir)Installers\Latest\ProductSetup.wixpdb" -out
"$(ProjectDir)Obj\ProductSetup.wixmst"
"$(WIX)Bin\candle.exe" "$(ProjectDir)ProductPatch.wxs" -out
"$(ProjectDir)Obj\Pro
Some quick questions:
1. When calling torch, is the "-p" argument used? Without that, pyro may not
see the file or other data it needs to do its job.
2. Are the source paths in the two wixpdbs the same or different? Are the
wixpdbs "bound/binary" (so that the older version of the file is not
overw
To UNC:
Is possible during deferred, if you set the Impersonate attribute to "yes".
-Blair
-Original Message-
From: Fabio Di Lorenzo [mailto:fa...@dilorenzo.ch]
Sent: Thursday, September 16, 2010 2:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
#2 (ExternalUI) is UI in your bootstrapper exe. It calls MSI APIs to
register a callback method and it uses other MSI APIs to start the
installation. It does not launch MSIEXEC.EXE but uses MSI.DLL directly. This
allows you to have your own progress monitoring and your own "end" UI
instead of depen
I assume you logged MSI actions; what is the value of REQUIREDBINARIES
property? Also, I'm note sure you correctly use the upgradecode (ID tag from
the Upgrade element). That ID must be the UpgradeCode from the product you want
to detect wheter installed or not; do you have that GUID?
--- On
Hi Phil, thanks. Actually I wanted it that way, but I feel it's not the problem
at the moment.
Yet, as is my case, 2 features and the original installer installed Feature1, I
would like the upgrade to go directly upgrading the installed feature with no
UI displayed to select what feature to in
6 matches
Mail list logo
