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

[Jon Earle]

Thank you, Rob.


Are you able to provide insight into the question I asked?


________________________________
From: Rob Mensching <rob at firegiant.com>
Sent: Thursday, January 11, 2018 12:56 PM
To: WiX Toolset Users Mailing List
Cc: Jon Earle
Subject: RE: [wix-users] Custom Bootstrapper Application, command line usage - possible?

One thing to note: The wixba code is released under the MS-RL. Any changes you make to that code will need to be published.

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/
WiX Support | WiX Experts and Resources from FireGiant<http://www.firegiant.com/>
www.firegiant.com
WiX Support | Installation, Development, Deployment | WiX Experts and Resources from FireGiant




-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Jon Earle via wix-users
Sent: Thursday, January 11, 2018 6:43 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?

So I abandoned wixwpf as there were enogh differences between it and wixba that i figured i'd just toss my stuff into wixba and modify that.


So, I am there, now.  Was a bit of a chore to adapt wixba as the zipfile of source code could not be built - had to download the git repo.  After that, some manual modification of paths in projects allowed them to load, then began the task of ripping out functionality I don't need and adding that which I do.


Down now to deciding where to drop my code.  I am trying to understand the differences and similarities of RootViewModel and InstallationViewModel.  Why are there two view models?  Both seem to contain commands (Install contains the install/modify/uninstall, plus all the wix events and rootview contains a copy of the installationviewmodel and the commands for cancelling, plus some state.


Please help me to understand the design choices leading to these two models and what "flavour" of code should go in each?


Thanks!

Jon


________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Hoover, Jacob via wix-users <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] 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>
Cc: Edwin Castro <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> 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