1. /? is there. The WiX Standard Bootstrapper Application just doesn't
support it yet. You can see bits and pieces where it will go.

2. Yes, the XxxPackage/@Name can contain relative paths.

3. Right. The command-line is provided very early because you could
technically create different Bootstrapper Applications based on the switches
(for example a "passive" BA vs. a "full-UI" BA).

4. Yeah, that's a bug in the documentation. The term "User Experience" or
"UX" is still littered all over the place. We changed it to "Bootstrapper
Application" or "BA" because there was this constant confusion that the "UX"
(aka: "BA") only displayed UI. That is not the case. The BA drives the
process. Burn is just an engine that abstracts away a lot of the ugly lower
level details.

One of my primary goals with Burn was to build a bootstrapper that could
finally subsume all the boostrapper in Microsoft. Every team seems to have
their own home rolled bootstrapper (of various qualities) that do things a
little different from everyone else. Heck, Visual Studio has 5 (5!)
different bootstrapper it uses for itself. They are slowly centralizing on
Burn (it'll take a while).

The downside is that while the engine is powerful and flexible, there is
more work to do in layers above the engine. I made a big push through
November and December to get the standard bootstrapper application together
so that there was at least something with basic functionality and could
serve as an example. I also switched the WiX BA to be managed code to
demonstrate how to write a BA in WPF. That was actually pretty fun.
 Anyway, bits and pieces are all here and now its a matter of bringing them
together (fixing bugs). Then the primary focus can move out of the engine
and on to the WiX Standard BA to make it more configurable, prettier, etc.

And that is the method to the madness.


On Wed, Jan 12, 2011 at 12:42 PM, Vitalii Dolia <vdo...@hotmail.com> wrote:

>
>
> > From: r...@robmensching.com
> > Date: Tue, 11 Jan 2011 23:20:35 -0800
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Running Burn-driven installer in quiet mode
> (command line parameters)
> >
> > 1. Yes, absolutely. Burn supports parsing the "standard package switches"
>
> It would be nice to add one more, "/?", just to be able to check the list
> of available "standard package switches" or even show the options from a
> bootstrapper application DLL used.
>
> > 2. The complete list is dependent on the Bootstrapper Application you
> pick.
> > The wixstdba supports only the "standard package switches":
> [...]
> > -layout = create a local image of the bootstrapper (i.e. download files
> so
> > they can be burned to DVD)
>
> What's the directory structure for the resulting local image? Does
> MsiPackage/@Name attribute responsible for that?
>
> > 3. Yes, as noted above extra command-line parameters are passed to the
> > BootstrapperApplication and it can set Variables to flow into Chained
> > Packages (ExePackage XxxCommand attributes or MsiPackage/MsiProperty
> > element).
>
> I see now. It's a BOOTSTRAPPER_COMMAND parameter of
> BootstrapperApplicationCreate function.
>
> One more thing. In documentation I've seen a notice of IBurnUserExperience
> interface ("Building a Bootstrapper Application for Burn" chapter), but
> couldn't find a reference to it in WiX source code. Has the interface been
> replaced by IBootstrapperApplication and it's just a documentation bug? I do
> understand that the current documentation on Burn is incomplete, so I'll dig
> into WiX source files a little bit.
>
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to