I'm not sure if my previous reply went through, so I'll try again. My first
try was using the standard bootstrapper, and after looking through more of the
source found that the UI level is being set in the engine in
MsiEngineCalculateInstallLevel. There is related code in
MsiEnginePlanAddPac
Thanks ! Yes, it's using the standard bootstrapper.
In the meantime I hunted through the source and found
MsiEngineCalculateInstallLevel, MsiEnginePlanAddPackage and
WiuInitializeExternalUI.. wondering if there is a good way to intercept the
UI level in a custom BA. Maybe using IBootstrapperEn
Which BootstrapperApplication are you using? If you're using wixstdba, I
expect it does not handle this scenario well. You'd want to create a BA
that is designed to show the MSI UI instead of it's own UI.
On Thu, Mar 22, 2012 at 9:17 AM, wrote:
> Some further research after looking at some logs
Some further research after looking at some logs : when I install the .msi via
"msiexec /I msiFileName.msi", CLIENTUILEVEL=0, which I guess is full UI. When
uninstalling via the command line below, CLIENTUILEVEL=2 and UILevel=3
(INSTALLUILEVEL_BASIC).
So I guess my question is how to get burn
Hi all -- I've been tinkering with Wix 3.6 (build 2719), and set up a test
bundle which installs a .msi package. I wanted the msi's user interface to be
displayed, so I specified DisplayInternalUI="yes" in MsiPackage. This all
seems to work fine for installation.
On uninstallation I wanted to
5 matches
Mail list logo