[wix-users] Optional passing of BootStrapper /q option to ExePackage

[rpapo at comcast.net]

Resolved.  See
https://stackoverflow.com/questions/43896727/how-to-use-burn-built-in-variab
le-wixbundleuilevel-in-a-commandline-elements-con

--Rick Papo

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Rick
Papo via wix-users
Sent: Friday, December 4, 2020 8:44 AM
To: 'WiX Toolset Users Mailing List' <wix-users at lists.wixtoolset.org>
Cc: rpapo at comcast.net
Subject: [wix-users] Optional passing of BootStrapper /q option to
ExePackage

I've looked around a bit, but have not found a clear answer to this question
online: is it possible to pass the /quiet option from the bootstrapper
application command line down to an ExePackage command line?  In general,
people seem to be passing /quiet (or its equivalent) down to ExePackage
command lines explicitly.  Hard coding it.  But I am installing a VSIX,
using the VSIX installer helper, from the bootstrapper application because I
have found that it sometimes dies mysteriously if it is done from the MSI.
That is, it sometimes causes recursion in the Windows Installer.  But I have
found that when installing VSIX packages, it is best to show the user
interface, because if there are errors due to portions of Visual Studio
remaining in memory, the automatic recovery and error generated in such
cases causes problems.  And besides, when that happens, the user gets no
clue as to what is going on.

But, I have a customer who wants a completely silent install, compliant with
the /quiet command line options for the bootstrapper.

Any ideas?

--Rick Papo


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant
http://www.firegiant.com/