Okay, done. https://sourceforge.net/p/wix/bugs/3116/ LaunchAction.Modify on
Present package does not call PlanMsiFeature
From: Bob Arnson
To: wix-users@lists.sourceforge.net
Sent: Tuesday, October 9, 2012 10:00 PM
Subject: Re: [WiX-users] Detecting Feature
On 09-Oct-12 14:23, Brian_Covington wrote:
> private void PlanPackageBegin(object sender, PlanPackageBeginEventArgs e)
Please file a bug on this -- I'd vote that it's a bug that the engine
doesn't call OnPlanMsiFeature; if it would and a feature state was
change, it would set the package action t
For those who are searching for an answer, this is what has worked for us:
private void PlanPackageBegin(object sender, PlanPackageBeginEventArgs e)
// if this is the package, which has optional features
if (e.PackageId.Equals("",
StringComparison.Ordinal))
{
// if the action b
On 03-Oct-12 18:03, tom wrote:
> Is this make sense to change the package state in the
> PlanPackageBegin event? i did it and the event is called.
Yes, that makes perfect sense.
--
sig://boB
http://joyofsetup.com/
--
Do
Looks like /LaunchAction.Modify/ does not modify the package state
and it stay in a None state
(I think Rob also mentioned it somewhere)
The engine Process Package function check if the package should be processed
//If the package is in a requested state, plan it.
if (BOOTSTRAPPER_REQUEST_STATE
On 02-Oct-12 08:40, Brian_Covington wrote:
> Yes, that is what I am expected to see, but I do not see anything. If you
> look at the log, you can see where I "clicked" the checkbox, which sets the
> string variable AddLocalSet on the Engine, but the PlanMsiFeature, where I
> look at what checkboxe
Yes, that is what I am expected to see, but I do not see anything. If you
look at the log, you can see where I "clicked" the checkbox, which sets the
string variable AddLocalSet on the Engine, but the PlanMsiFeature, where I
look at what checkboxes are checked and attempt to alter the Feature stat
On 01-Oct-12 10:33, Brian_Covington wrote:
> I have the same code in the DetectMsiFeature and, both get called in the
> initial installation. However, when I run the bootstrap executable again
> (or run Change in ARP) I do not get any calls to PlanMsiFeature, which is
> where I modify the feature
I have the same code in the DetectMsiFeature and, both get called in the
initial installation. However, when I run the bootstrap executable again
(or run Change in ARP) I do not get any calls to PlanMsiFeature, which is
where I modify the feature states based upon user input.
--
View this mes
Try "DetectMsiFeature"
I think you need to set the requested feature state in
PlanMsiFeature
Not sure though.
Tomer...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Detecting-Feature-state-in-Managed-BA-tp7580920p7580939.html
Sent from the w
I am trying, in my Managed Bootstrap Application, detect that my bundle is
already installed and that a few optional features are installed as well. I
wrote the code below, but I never get into the PlantMsiFeature code. I have
set the EnableFeatureSelection on my MsiPackage. Basically, the thi
11 matches
Mail list logo
