One very important clarification I want to make, the WiX Standard
Bootstrapper Application is *native* code. It will run on WinXP+ with no
dependencies.
The wixstdba is also somewhat customizable but definitely does not support
as much as the UI element does for MSI packages.
Most of the scenarios
thread that deserves
attention? E-Mail Me
--- On Wed, 1/12/11, Vitalii Dolia wrote:
> From: Vitalii Dolia
> Subject: Re: [WiX-users] Burn issue
> To: wix-users@lists.sourceforge.net
> Date: Wednesday, January 12, 2011, 5:59 PM
>
> > From: r...@robmensching.com
> From: r...@robmensching.com
> Date: Tue, 11 Jan 2011 23:13:34 -0800
[...]
> In your first example, I don't understand, why you have to create a UI in
> your MSI. Burn will show UI for all scenarios (install, repair, uninstall,
> upgrade patch) so you do not need a UI in your MSIs.
> I agree that
.
Daniel Moody | QA Engineer | Gibbs and Associates
Phone: 805-523-0004
Email:dani...@gibbscam.com
www.GibbsCAM.com
On 1/12/2011 12:11 AM, wix-users-requ...@lists.sourceforge.net wrote:
> Date: Tue, 11 Jan 2011 23:13:34 -0800
> From: Rob Mensching
> Subject: Re: [WiX-users] Burn issue
Again, Burn is more about creating a unified installation experience than
displaying a "collection of random installation experiences". I suggest
playing with Burn and seeing how it caches content for you then executes the
installs to better understand the flow and why I'm challenging the
assumptio
Rob Mensching robmensching.com> writes:
> Maybe. It's not really in the model Burn was designed for. Burn was intended
> to provide a seamless installation experience not pop up a bunch of
> different installation wizards.
[skipped]
> Burn is designed to provide
> the antithesis of that experienc
ilto:r...@robmensching.com]
> Sent: 05 January 2011 07:26
> To: chr...@deploymentengineering.com; General discussion for Windows
> Installer XML toolset.
> Subject: Re: [WiX-users] Burn issue
>
> IMHO, the Visual Studio install is an absolute mess. I hope to get the
> opportunity to really tackle
ut personally
> I prefer it the other way.
> Christopher Painter, Author of Deployment Engineering
> Blog<http://blog.deploymentengineering.com/>
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
> --- On *Wed,
y for each product).
-Nick
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 05 January 2011 07:26
To: chr...@deploymentengineering.com; General discussion for Windows Installer
XML toolset.
Subject: Re: [WiX-users] Burn issue
IMHO, the Visual Studio install
stopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Wed, 1/5/11, Rob Mensching wrote:
From: Rob Mensching
Subject: Re: [WiX-users] Burn issue
To: chr...@deploymentengineering.com, "Ge
You can also set conditions on Features directly. Or if you write your own
bootstrapper application, you can programmatically decide what to install on
the plan callbacks.
--
virtually, Rob Mensching - http://RobMensching.com LLC
On Tue, Jan 4, 2011 at 1:49 PM, jhennessey wrote:
>
> I haven't w
a "take it all off" experience?
>
> Chris
>
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
> --- On Tue, 1/4/11, Rob Mensching wrote:
>
> >
.@deploymentengineering.com]
> Sent: 04 January 2011 17:35
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn issue
>
>
> Rob,
>
> That's an interesting comment but it makes me think of the Visual Studio
> experience. It
I haven't worked with burn yet but from what I can tell it looks like you
would just set a burn variable to be passed to the MSI. So to install a set
a features you could just set the ADDLOCAL property as appropriate (in your
custom UI). You could also just split your large MSI into separate MSIs
everything?
Cheers
Sean.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 04 January 2011 17:35
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn issue
Rob,
That's an interesting comment but it makes me
ves
attention? E-Mail Me
--- On Tue, 1/4/11, Rob Mensching wrote:
> From: Rob Mensching
> Subject: Re: [WiX-users] Burn issue
> To: "General discussion for Windows Installer XML toolset."
>
> Date: Tuesday, January 4, 2011, 10:39 AM
> Maybe. It's not really in
at 10:22 AM, Sean Farrow
wrote:
> Could this be added?
> Cheers
> Sean.
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 03 January 2011 16:29
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users]
Could this be added?
Cheers
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 03 January 2011 16:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn issue
No. Burn doesn't show the UI from the MSIs.
On Sun,
No. Burn doesn't show the UI from the MSIs.
On Sun, Jan 2, 2011 at 3:28 AM, Sean Farrow wrote:
> Hi:
> I'm using Burn as a container to hold two msi's.
> I'd like to use the ui's from the msi in the current implementation.
> If I remove the bootstrapApplicationRef element I get a lght0001: the gi
19 matches
Mail list logo
