Madden, William wrote:
> "A custom action can't run another installer."
>
> This is only partially true, a custom action can run another installer if run
> from the UI sequence not the Execute sequence, only one install at a time can
> be within a execute sequence.
>
True. But not supporting
Still probably safer to use a bootstrapper rather than a pseudo-nested
install.
Thomas S. Trias
Senior Developer
Artizan Internet Services
http://www.artizan.com/
Original Message
Subject: Re: [WiX-users] Calling a external setup package
From: Madden, William
To: General
rnson [mailto:b...@joyofsetup.com]
Sent: Thursday, April 09, 2009 7:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Calling a external setup package
Yu, Brian wrote:
> Is it still the case where WIX don't really support it? Even with using
> cust
Yu, Brian wrote:
> Is it still the case where WIX don't really support it? Even with using
> custom action?
>
A custom action can't run another installer.
--
sig://boB
http://joyofsetup.com/
--
This SF.net email i
I'll try and learn how to use dotnetinstaller
Brian
-Original Message-
From: dB. [mailto:dbl...@dblock.org]
Sent: 19 March 2009 12:18
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Calling a external setup package
On an even more positive note thi
: Thursday, March 19, 2009 2:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Calling a external setup package
Hey Jim,
There is not an "official" way to do this at the time. You could develop
your own "bootstrapper" that would launch the se
Hey Jim,
There is not an "official" way to do this at the time. You could develop
your own "bootstrapper" that would launch the sequence. It is highly
recommend that you don't use a custom action to launch a secondary process
while installing.
On a positive note, WIX is currently in the process o
7 matches
Mail list logo
