[wix-users] Disallowing bootstrapper UI install

[Griesshammer, Christoph (GE Healthcare)]

Thank you for your informative answer.

I'm sorry for my beginners' knowledge of bootstrappers, but I was wondering if you or anyone else have any good tutorials of how to achieve this type of work? I'm wondering how I exactly extend the existing WixStdBa to implement OnDetectBegin.

Christoph

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Phill Hogland
Sent: Friday, August 28, 2015 1:14 PM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Disallowing bootstrapper UI install

You can use your BA's reference to the Wix Command.Display object to determine whether it was launched in silent or with a display.  And you can use Command.GetCommandLineArgs to get the (none burn) parameters which were passed in and provide logic if required command line switches are missing (with or without a display).  And if you want to see the command line as it was before Burn parsed it, you call system APIs.  If using the WixStdBa add a c++ bafunctions.dll and implement you logic in OnDetectBegin,  or certainly by OnDetectComplete, which could present a message box or set an engine variable which is then acted on by a bal;Condition statement.  (I did something similar a few years back before converting to a custom BA, which provides even more flexibility for these scenarios.)

Phill

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Griesshammer, Christoph (GE Healthcare)
Sent: Friday, August 28, 2015 11:44 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Disallowing bootstrapper UI install

I am trying to set a condition on a bootstrapper to disallow a UI install.

The reason for this, is that the .exe should only be used for a push installation called silently.

However, we do not want anyone getting their hands on the .exe and trying to install it by just double-clicking, as they are ignoring some command-line options.

We are near the end of a release, so I don't have time to make a robust UI and properly test it, hence I am trying to just remove the UI install completely.

Ideally, it'd be as simple as:

<bal:Condition Message="This installer can only be run in silent mode.">UILevel = 2</bal:Condition>

But I see that this is an MSI property and we can't utilize it here.

Looking at the log file, I can't see any property that would let me achieve this.

Any help?

Christoph Griesshammer


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant https://urldefense.proofpoint.com/v2/url?u=http-3A__www.firegiant.com_&d=BQICAg&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-l6_npd-dx-ekbVSbypvaw-IcErQ11UE3f78jQgrCDw&m=aOMFT39-gBP5qbzQRGCpfa7wZCLT78W4ghz-McJZKzI&s=ZEDeZZ-EfsKNZsnfCXgGhVTX8yX6AP2gmkAReduSjro&e= 

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant https://urldefense.proofpoint.com/v2/url?u=http-3A__www.firegiant.com_&d=BQICAg&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-l6_npd-dx-ekbVSbypvaw-IcErQ11UE3f78jQgrCDw&m=aOMFT39-gBP5qbzQRGCpfa7wZCLT78W4ghz-McJZKzI&s=ZEDeZZ-EfsKNZsnfCXgGhVTX8yX6AP2gmkAReduSjro&e=