Cool, thanks for confirming.
On Sun, Jan 6, 2013 at 11:54 PM, Amadeus wrote:
> Hello again,
>
> Just posting to let you know I found (and fixed) the issue. We had custom
> behavior in the PlanPackageBegin event that lets us remove packages based
> on
> user types. This messed up Burn's upgrade
Hello again,
Just posting to let you know I found (and fixed) the issue. We had custom
behavior in the PlanPackageBegin event that lets us remove packages based on
user types. This messed up Burn's upgrade scenario, and simply not running
this on a detected upgrade solved the issue.
Cheers,
Amade
Thanks for you reply. I'm going to investigate that possibility, but I think
it's unlikely we have the same cause of this issue (I don't think this MSI
has several features to select from).
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSIPackage
]
Sent: 20 December 2012 10:25 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MSIPackage unregistering dependency to bundle
I've tested some more and during installation and upgrade I checked the
Installer/Dependencies location in the registry.
During installation, all pac
I've tested some more and during installation and upgrade I checked the
Installer/Dependencies location in the registry.
During installation, all packages are correctly put there as dependent to my
installer.
During upgrade, all packages - except one - are put there as dependent to my
installer.
Hello,
I have an odd problem. It's not /really/ related to Burn and I believe the
problem lies with the MSI - but I think (hope) you can help me out.
My scenario is this:
When I upgrade the Bootstrapper one of the MSI Packages is always detected
as *not* having a dependency to the old Bootstrappe
6 matches
Mail list logo
