Ahh!!
That is really in detail and most helpful. Thank you very much for the
helpful links and in details.
Regards,
Sampat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-suppress-the-StdBA-Bootstrapper-UI-tp7597705p7597819.html
Sent from
Regarding using BAFunctions.dll for DelayStart, it has been about a year
since I used that feature and then abandoned that code in favor of creating
a WPF managed BA (which I would also recommend, but you could use any UX
framework - MFC, WCF, Java?smile/). But as I recall the basic steps are:
1)
@lists.sourceforge.net
Subject: [WiX-users] How to suppress the StdBA Bootstrapper UI
Hi,
I have chained a single msi package(with DisplayInternalUI option being
true) inside the StdBA using wix 3.9 toolset. My questions are as follows,
1). Can we *suppress the small StdBA UI* which
]
Sent: Tuesday, November 4, 2014 6:56 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] How to suppress the StdBA Bootstrapper UI
1) Not what it was designed to do. Instead of trying to fight burn, why not try
to embrace it. Create a single unified user experience in the BA
Hi Hoover, Jacob,
Thank you very much for your suggestions.
We have 5 components of our product. 2 are the main components and 3 are the
client tools for interaction. The 2 main comps should take 2 users-details
as input (domain, usrname n pwd) (which ll later ,during installation, be
qualified
HI,
Can we add something that skips the cpu cycles and that adds some delay
before the Detect is Completed. So that this gives an impression like the
splash stays for some amount of time?(Just a vague idea).
Any thoughts?
Regards,
Sampat.
--
View this message in context:
: Re: [WiX-users] How to suppress the StdBA Bootstrapper UI
HI,
Can we add something that skips the cpu cycles and that adds some delay before
the Detect is Completed. So that this gives an impression like the splash
stays for some amount of time?(Just a vague idea).
Any thoughts?
Regards
Ohh!! Sounds great!!Nice to know about this.
So, i will quickly add a custom action which will have a sleep() for some
amount of time.
@Rob: Thanks for the confirmation. Could you please share the approaches for
dealing with the changes have to be done to build a older version
.wixproj(created
I agree with Jacob's recommendation that writing a mba to display your UX and
hide or don't implement the UX in each msi (or exe prereq like VC) is much
prefered. This approach works great and is much better than fighting the
intended design of burn. The wix source includes a good example
Ahh!!
Thanks for the MsiProperty :) . Later i realized it and now the way is
clear for me. :)
For UIs, which among the following i have to choose
1. ThemeFiles(.xml) or
2. WPF
?
Thanks for the BAFunctions. I tried adding reference to BAFunctions alone to
use the Delay() Function, but got error
Hi,
I have chained a single msi package(with DisplayInternalUI option being
true) inside the StdBA using wix 3.9 toolset. My questions are as follows,
1). Can we *suppress the small StdBA UI* which will be displayed in the
background till the installation of chained msi completes.? In this case
11 matches
Mail list logo
