[wix-users] Custom Bootstrapper Application, command line usage - possible?

[Jon Earle]

Hey Jacob,


So I got that far... figured out that Command just needed to be referenced by itself.


So, I now have the gui hidden, but nothing happens.  Task Manager just shows the installer in memory and nothing is installed.  Is there something else I need?  Looking at the wixba code, I gather I need to kick things off, but am not really sure how ... calling Plan from DetectComplete?


Do I need to handle the commandline arguments myself or is there already a mechanism in the engine to do that?


Just have no idea how much I need to implement or vs how much is implemented by wix...


Cheers!

JOn


________________________________
From: Hoover, Jacob <Jacob.Hoover at greenheck.com>
Sent: Tuesday, January 9, 2018 1:02 PM
To: WiX Toolset Users Mailing List
Cc: Jon Earle
Subject: RE: [wix-users] Custom Bootstrapper Application, command line usage - possible?

One of the classes in WixWPF is going to inherit from BootstrapperApplication, and that's the reference you need.  I haven't looked at WixWPF, so you're going to need to search the code for it, or ask the developer of it for it.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Jon Earle via wix-users
Sent: Tuesday, January 9, 2018 9:42 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Jon Earle <earlej at hotmail.com>
Subject: Re: [wix-users] Custom Bootstrapper Application, command line usage - possible?

Sorry , I seem to need a bit more guidance...


I am attempting to retrofit WixWPF to include that functionality, but, I am getting an error in the VS IDE that states that an object reference is required for

BootstrapperApplication.Command.

Which reference do I need to include to gain that?

I also attempted to include the Model object from WixBA, but again, I receive an error stating that UX is not a member of Microsoft.Tools.WindowsInstallerXml.

Thanks for a bit more help!

Jon


________________________________
From: kaveeshd at gmail.com <kaveeshd at gmail.com> on behalf of Kaveesh Dashora <kaveeshd at googlemail.com>
Sent: Monday, January 8, 2018 10:24 PM
To: WiX Toolset Users Mailing List
Cc: Jon Earle
Subject: Re: [wix-users] Custom Bootstrapper Application, command line usage - possible?

Display is set based on the command line parameters. Providing a silent at command line would mean a value of passive.

You can then work out your BA to display the UI or not.

On Jan 9, 2018 4:50 AM, "Jon Earle via wix-users" <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>> wrote:
Hey Jacob,


How is the BootstrapperApplication.Command.Display being set?


________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org>> on behalf of Hoover, Jacob via wix-users <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Sent: Monday, January 8, 2018 4:51 PM
To: WiX Toolset Users Mailing List
Cc: Hoover, Jacob
Subject: Re: [wix-users] Custom Bootstrapper Application, command line usage - possible?

Your BA has to handle it...

BootstrapperApplication. Command.Display == Display.Passive || BootstrapperApplication.Command.Display == Display.Full

You can see how the Wix BA does this inside of WixBA.cs, in the Run method.

I'm not certain, but you may also need to implement the parsing of args to handle setting variables as well (since WixStdBA has code in it to do so).

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org>] On Behalf Of Edwin Castro via wix-users
Sent: Monday, January 8, 2018 3:44 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Cc: Edwin Castro <egcastr at gmail.com<mailto:egcastr at gmail.com>>
Subject: Re: [wix-users] Custom Bootstrapper Application, command line usage - possible?

What do you mean by "We could run it when using the standard BA"?

I use the standard BA as well and when I run it from the command line the GUI just pops up and the command line returns as expected for a Windows application. If I want to wait until the bootstrapper completes I need to execute it using start /wait.

--
Edwin G. Castro


On Mon, Jan 8, 2018 at 1:39 PM, Jon Earle via wix-users < wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>> wrote:

> Hey folks,
>
>
> I have concocted a custom bootstrapper application, using the WixWPF
> framework (https://github.com/tpalacino/WixWPF), which is working
> quite well.  The problem I am having, is running the installer via commandline.
> We could run it when using the standard BA but, when I issue the same
> commandline now, the GUI just pops up.
>
>
> Commandline:
>
>
> Client.exe /install /quiet /l install.log ADDLOCAL="myFeature"
> INSTALLDIR="c:\client"
>
>
> Is there anything I need to implement in the bootstrapper code to
> enable commandline usage?
>
>
> Cheers!
>
> Jon
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>

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

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

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

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