I had the same problem. What I did to solve it is in the product msi, I
created a custom action that runs on both install and uninstall to find the
bundle entry in Uninstall and update the DisplayVersion. When installing, I
create an OldDisplayVersion which has the version number for what is abou
Sorry, no. We are weeks away from having to release and the plan for now is to
not use cumulative patches.
From: Tomer Cohen [via Windows Installer XML (WiX) toolset]
To: Brian_Covington
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed
Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2).
I am changing the bundle version as well as the version of the msi, but
still the second patch for the bundle appears alongside the first one, not
replacing it as I would expect.
Do I need to do something to "
Forgive me, but, I do not quite understand what you are asking. The first
application is dependant upon the second and cannot exist in singular (i.e.
it is built on top of the others' dlls).
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-
Hi all,
I have created a managed bootstrapper to install my 2 product msis. I
have peared down the source of this bootstrapper to create a patch
bootstrapper, to install the msp files for these products. Everything works
as expected until I try to install the second patch. It installs along si
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
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
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
8 matches
Mail list logo
