Hi,
With the update, i have used the Apply method like below.
this.Engine.CloseSplashScreen();
var pl = new PlanMsiFeatureEventArgs("Wixdata", "Install",
FeatureState.Source);
Engine.Detect();
this.hwnd = IntPtr.Zero;
Engine.Plan(LaunchAction.Install);
Engine.Apply(this.hwnd
1. Your MsiPackage DisplayInternalUI attribute is probably set to "yes".
2. Check out the WixBA at src\Setup\WixBA. It is a full implementation of a
managed BA.
On Fri, Jun 1, 2012 at 12:31 AM, Kannan24 wrote:
> Hi,
>
> With the update, i have used the Apply method like below.
>
>
> this.Engin
I'm still getting more bug reports from users about this, even with our
caveat/known issues...
On Fri, May 25, 2012 at 8:17 PM, imran wrote:
> Did anyone resolve this issue? I am getting the same problem in Windows XP.
>
> --
> View this message in context:
> http://windows-installer-xml-wix-too
Hi,
I need to manipulate a string, stored in a property.
Fist I was thinking about using a custom action read one property and
writing the result of the string manipulation to an other one.
The problem that I discovered is, that the string, which has to be
manipulated, is a result of a registr
Hi,
I was looking at this earlier. Found this link which gives an example:
http://kobyk.wordpress.com/2008/10/21/installing-filter-drivers-with-difxapp-and-a-wix-v3-msi/
Never got around to using it yet, though.
Wes
From: Bill Miller [billmil...@tness.co
I am trying to create shortcuts to uninstalling whatever the bootstrapper
has installed. So simply i want to do the same thing as the uninstall does
when going to Add and remove programs.
I found that de bootstrapper is installed in package
cache{guid}[bootstrappername].exe
One of the msi package
Rob,
Thank you so much. Have a wonderful day.:)
Regards,
Lily Lee
Mobile: +1 (949) 468-7759
Support Hotline: +1 (949) 916 6802
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, May 31, 2012 5:10 PM
To: General discussion for Windows Installer XML tool
I have an MSI package that detects the VSTO runtime via an entry in the
Upgrade table (I just use it for a launch condition in the MSI.)
When burn detects the related MSIs for this package it finds the VSTO
runtime and indicates that the operation is a "MajorUpgrade". This seems a
bit odd to me. S
8 matches
Mail list logo
