You can't display a feature tree, but it does support adding checkboxes to the
options page which can be used to select features.
--
Bruce Cran
Sent from my iPhone
On 31 Jan 2013, at 17:54, Karl Werner wrote:
> Can you have the wix standard bootstrapper prompt the user for feature
> selectio
ssible situations (installs/upgrades/repairs/etc).
>
>
> -Original Message-
> From: Karl Werner [mailto:karl.wer...@gmail.com]
> Sent: Thursday, January 31, 2013 11:54 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Redisplay MSI's UI
sion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Redisplay MSI's UI when Bootstrapper is run a second
time
Can you have the wix standard bootstrapper prompt the user for feature
selection? I haven't seen it do that . . .
On Thu, Jan 31, 2013 at 11:05 AM, Rob Mensching wro
Can you have the wix standard bootstrapper prompt the user for feature
selection? I haven't seen it do that . . .
On Thu, Jan 31, 2013 at 11:05 AM, Rob Mensching wrote:
> You can modify feature states via the BootstrapperApplication.
>
>
> On Thu, Jan 31, 2013 at 8:44 AM, Karl Werner
> wrote:
>
ndows Installer XML toolset.
Subject: Re: [WiX-users] Redisplay MSI's UI when Bootstrapper is run a second
time
You can modify feature states via the BootstrapperApplication.
On Thu, Jan 31, 2013 at 8:44 AM, Karl Werner wrote:
> To close the loop on this, I ended up doing the fol
You can modify feature states via the BootstrapperApplication.
On Thu, Jan 31, 2013 at 8:44 AM, Karl Werner wrote:
> To close the loop on this, I ended up doing the following:
>
> 1) Reverting to the Wix Standard Bootstrapper. (There is probably a way to
> get my custom bootstrapper to work, bu
To close the loop on this, I ended up doing the following:
1) Reverting to the Wix Standard Bootstrapper. (There is probably a way to
get my custom bootstrapper to work, but I exhausted enough time trying to
figure it out. Somehow the Wix Standard Bootstrapper knows what mode to go
into early in
Do basically there is no way to simulate the old bootstrapper from the old
vdproj setup projects? It would be nice if we could configure for this
behavior. I would expect many other shops would want the same behavior . . .
Maybe something like an attribute on MSIPackage that is equivalent to
"alw
On 29-Jan-13 16:10, Karl Werner wrote:
> However, still stuck on the original problem -> How can I get the MSI's UI
> invoked on the second run of the bootstrapper.
You can't. Burn needs to know the operation being performed which it
can't if the operation is determined during the execution of the
. .
> > >> Even if I take the InstallCondition out along with the second
> > >> MsiPackage, I still don't get the UI on the second run of the
> > bootstrapper.
> > >>
> > >> Thanks!
> > >>
> > >> Karl
> >
the
> bootstrapper.
> >>
> >> Thanks!
> >>
> >> Karl
> >>
> >>
> >> On Tue, Jan 29, 2013 at 10:05 AM, Hoover, Jacob <
> >> jacob.hoo...@greenheck.com> wrote:
> >>
> >>> My guess would be because you a
or both packages.
>
> -Original Message-
> From: Karl Werner [mailto:karl.wer...@gmail.com]
> Sent: Tuesday, January 29, 2013 11:12 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Redisplay MSI's UI when Bootstrapper is run a
> se
Windows Installer XML toolset.
Subject: Re: [WiX-users] Redisplay MSI's UI when Bootstrapper is run a second
time
While I'm still stuck on the core issue here of not being able to redisplay the
UI from the bootstrapper, I thought I'd document another way around the
ancillary uninstal
d time, the 32bit MsiPackage is going to detect based on upgrade code.
>>> Because your InstallCondition evaluates to false, it schedules the removal
>>> of it.
>>>
>>> -----Original Message-----
>>> From: Karl Werner [mailto:karl.wer...@gmail.com]
>>
-
>> From: Karl Werner [mailto:karl.wer...@gmail.com]
>> Sent: Tuesday, January 29, 2013 9:32 AM
>> To: wix-users@lists.sourceforge.net
>> Subject: Re: [WiX-users] Redisplay MSI's UI when Bootstrapper is run a
>> second time
>>
>> There appear to
code.
> Because your InstallCondition evaluates to false, it schedules the removal
> of it.
>
> -Original Message-
> From: Karl Werner [mailto:karl.wer...@gmail.com]
> Sent: Tuesday, January 29, 2013 9:32 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users]
...@gmail.com]
Sent: Tuesday, January 29, 2013 9:32 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Redisplay MSI's UI when Bootstrapper is run a second
time
There appear to be 2 distinct problems here:
1) MSI's UI is not redisplayed on subsequent bootstrapper execution.
There appear to be 2 distinct problems here:
1) MSI's UI is not redisplayed on subsequent bootstrapper execution.
2) Install Conditions are not behaving as I expect.
I've discovered that the uninstall is happening because I have two msi
packages, one for 64-bit, and another for 32-bit. These msi'
Currently we have a Wix Bundle that provides minimal interaction through a
custom .Net UI. We don't have the Bundle name set so the bootstrapper
won't get registered in ARP (by design). It then chains some pre-rquisites
and our product. Our product is an MsiPackage, something like this:
19 matches
Mail list logo
