I found the reason.
MSI can only set the property to NULL (aka Not set) when a checkbox is
unselected.
So remove the line (which actually
make the checkbox checked), and everything works fine.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/W
Hi,
I have some SetProperty code need to be executed after LaunchCondition, e.g.
To make the Product.wxs file clean, I added a new file Prepare.wxs, and move
the SetProperty code into that file, under the Fragment element.
However, I found the SetProperty does not get executed when I put it in
Are there any workarounds?
Seems to me this is a very common scenario.
Thanks,
-Elfe
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Edit-Control-trap-textchanged-possible-tp2907541p5224744.html
Sent from the wix-users mailing list archive at Nabbl
The idea behind fragments is that they supply blocks of authoring (aka code)
that are included or excluded as units. They allow you to build entire
libraries of authoring that are at your disposal without having to have all
of them included. Only those fragments that contain elements referenced fro
Unfortunately Windows Installer does not publish any events from its Edit
control. It does update the property associated with the control, but only
when the control loses the focus.
The only "reasonable" workarounds I see are:
1. You can compare two properties to see if the property was changed
Hi
I have a custom action that closes my app when its feature is being
uninstalled. Here's my code:
For some reason the action gets triggered during "Repair" and also when
ANOTHER feature is being uninstalled. Why is this happening? Doesn't my
condition mean "if MyAppFeature is installed, an
If your feature won't be affected at all by the transaction (such as when
removing a different feature) &MyAppFeature may very well be -1, which would
make your condition be true.
-Original Message-
From: Ivo Beltchev [mailto:i...@roadrunner.com]
Sent: Saturday, June 26, 2010 8:11 AM
To:
Hmm... could be.
Is it possible that &MyAppFeature is not initialized yet because I'm
running before "InstallValidate"? I have to run before InstallValidate,
because I want to run before the Restart Manager pops up and asks to
close the app for me.
What is the recommended way to debug such prob
On 6/22/2010 10:29 AM, Stefan Kuhr wrote:
> So what would then be a proper solution for my problem? I have PNG
> files (so
> theses are unversioned by definition) that I always want to replace with
> those from my install, even if the customer replaced them with his own files
> in the older versio
On 6/21/2010 9:24 PM, Castro, Edwin G. (Hillsboro) wrote:
> The WiX help file says the following about custom binder variables:
>
Ack, bad. It's worded poorly (and bits are wrong). Please file a bug.
> How do I specify a value for !(bind.AssemblyVersion)?
>
You don't -- the only custom b
On 6/25/2010 3:48 PM, Castro, Edwin G. (Hillsboro) wrote:
> Does anybody know under what circumstances SchedXmlFile would schedule
> ExecXmlFile during uninstall?
>
Pretty much always. In general, use XmlFile with Permanent="yes" for
files you're installing and XmlConfig when you need to mod
&MyAppFeature is documented to be -1 when MyAppFeature will be left alone by
the installation transaction.
From: http://msdn.microsoft.com/library/aa368012.aspx
INSTALLSTATE_UNKNOWN -1 No action to be taken on the feature or component.
-Original Message-
From: Ivo Beltchev [mailto:i...@r
12 matches
Mail list logo
