I think the behavior could be implemented easily in WixStdBA using a BA
Function (in Wix 3.8 or in Wix 3.7 with WixExtendedBA). I went down that
route before I, for other reasons, decided to implement a mba. I actually
prefer the wixStdBA and BA Functions, but the business wants XAML in a mba.
h
Thanks Bob,
We'll continue to use the msistuff setup.exe bootstrapper for now, until we
find time to develop our own custom managed boostrapper application.
It'd probably be a useful feature to add in a future version of WiX.
Thanks again.
John
On 29 October 2013 01:32, Bob Arnson wrote:
>
On 26-Oct-13 05:15, John Ludlow wrote:
> I don't think the standard bootstapper application's theming is capable of
> that kind of customisation.
That's correct. It would have to be a feature of WixStdBA.
--
sig://boB
http://joyofsetup.com/
--
Thanks but that's not the behaviour I need. Perhaps my explanation wasn't
clear.
The behaviour that I need is that when a particular registry entry exists
the install location control is disabled so that the user cannot change the
install directory. If the registry entry is not present then they c
When the user selects another folder the variable is updated.
On 25 Oct 2013 00:47, "John Ludlow" wrote:
> Thanks for that
>
> Does that prevent the user from selecting another folder?
>
> Thanks again
>
>
> On 24 October 2013 17:10, santhosh yalamuri wrote:
>
> > We have to set InstallFolder va
Thanks for that
Does that prevent the user from selecting another folder?
Thanks again
On 24 October 2013 17:10, santhosh yalamuri wrote:
> We have to set InstallFolder variable in burn bootstrapper.
>
> Example: Type="string"
> Value=""/>
>
>
> On Thu, Oct 24,
We have to set InstallFolder variable in burn bootstrapper.
Example:
On Thu, Oct 24, 2013 at 3:31 PM, John Ludlow wrote:
> Hi all,
>
> We have an MSI for a client application which, if you have the server
> installed on the same system, must be installed in the same directory as
> the server
7 matches
Mail list logo
