fusion.com]
Sent: 31 December 2012 08:46
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn, MsiPackage and DisplayInternalUI
Hi Peter,
I was created the feature request on 10th July, but no progress still. Could
you please follow up this feature, since we have close to releas
Hi Peter,
I was created the feature request on 10th July, but no progress still. Could
you please follow up this feature, since we have close to release.
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPackage-and-DisplayIn
To request a new feature, please use this link
http://sourceforge.net/tracker/?group_id=105970&atid=642717
-Original Message-
From: Kannan24 [mailto:skan...@syncfusion.com]
Sent: 09 July 2012 13:20
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn, MsiPackage
Hi,
Could you please update for the InternalUI, to change the values from
BA.dll?
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPackage-and-DisplayInternalUI-tp7484106p7579353.html
Sent from the wix-users mailing list archi
Hi,
I have planned to install the setup with managed UI and command line with
basic UI. When i try install with managed UI need to set the
DisplayInternalUI="no" and for command line need to show the basic UI, for
that set the DisplayInternalUI as "yes".
Thanks,
Kannan
--
View this message in co
On Jun 28, 2012; 1:17pm Rob Mensching-7 wrote:
/1. The "resuming" error message on Repair sounds like a bug. Can you make
sure you are on a very recent build of WiX v3.6 (things were fixed around
that area recently) and if that still happens, open a bug./
I've logged bug 3538817.
/2. " I get the
That is not supported today. Why would you need to do this?
On Wed, Jun 27, 2012 at 8:47 PM, Kannan24 wrote:
> Hi,
>
> I need to change the DisplayInternalUI at run time in BA. Unable to find
> the
> DisplayInternalUI property in BA. Please, how to set the DisplayInternalUI
> property in BA?
>
>
1. The "resuming" error message on Repair sounds like a bug. Can you make
sure you are on a very recent build of WiX v3.6 (things were fixed around
that area recently) and if that still happens, open a bug.
2. " I get the impression from what you are saying here and in other posts
that you are lea
Hi,
I need to change the DisplayInternalUI at run time in BA. Unable to find the
DisplayInternalUI property in BA. Please, how to set the DisplayInternalUI
property in BA?
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPacka
Rob Mensching-7 wrote
>
> The wixstdba isn't designed to show the internal MSI UI. You'll probably
> want to make a custom BA that is designed to show the internal MSI UI.
>
Could you provide more detail about this? My simple test case sets
DisplayInternalUI="yes" for my MSI package that is bas
You set DisplayInternalUI at build time.
On Tue, Jun 26, 2012 at 10:00 PM, Kannan24 wrote:
> Hi,
>
> I need to set the DisplayInternalUI value to "No" using BA.dll.
>
>
> SourceFile="D:\Work\Build\syncfusionessentialstudiosetup\EssentialStudioSetup\bin\Debug\EssentialStudioSetup.msi"
> Compress
Hi,
I need to set the DisplayInternalUI value to "No" using BA.dll.
In my Bundle.wxs DisplayInternalUI has set to Yes for command line
installation, but i need to set the DisplayInternalUI to "No" in managed
code (BA.dll). In Bootstrapper application have the external UI, so i need
to disable t
If I set DisplayInternalUI to "no" my message box is indeed displayed.
However the other two problem still occur: clicking on the link
FailureLogFileLink or the "close" button has no effect.
Actually the problem comes from using a custom theme file:
If I omit this line the standard theme is use
The wixstdba isn't designed to show the internal MSI UI. You'll probably
want to make a custom BA that is designed to show the internal MSI UI.
On Fri, Apr 20, 2012 at 4:48 AM, Bertrand D wrote:
> Hi there,
>
>
> As I want my msi to have its own ui, I defined in my bundle.wxs file (burn
> bootst
Hi there,
As I want my msi to have its own ui, I defined in my bundle.wxs file (burn
bootstrapper project which references the WixBalExtension):
The setup project UI is defined as:
When I execute the bootstrapper it works as expected until my msi is called.
Then I have two windows: the boo
15 matches
Mail list logo