[wix-users] DetectRelatedMsiPackage

[Brian C Cooke]

BootstrapperApplication class in burn has a DetectRelatedMsiPackage event.
I am subscribing to it and examining the arguments from my BA.

I am still searching for an answer why this event should fire with same
package ID and different product codes as its args.  My bundle definitely
has two different package IDs and two different product codes.  It is a
problem for me as I am trying to migrate features from one major upgrade to
the next.  In order to do this, I need the correct package ID.

Thanks,
Brian

> Can you please tell how you got the that debugging result?
>
> When you do an upgrade, burn will install your new bundle (running detect, plan, execute, etc.) and then by default, uninstall your old bundle (running detect, plan, execute, etc.). That might be something you need to pay attention.
>
>
On Mon, Jul 4, 2016 at 2:52 PM, Brian C Cooke <tonic889 at gmail.com> wrote:

> Yes, that makes sense.  But my question is why is detectRelatedMsiPackage
> event firing with the same package ID and different product codes?  It
> seems like it is either a Wix bug or a bug in the way my packages are
> authored.
>
> Thanks,
> Brian
>
> On Fri, Jul 1, 2016 at 7:21 PM, Huy Doan <hdoan at vmware.com> wrote:
>
>> I am not sure but from my understanding, the upgrade code is used to
>> detect related components during the upgrade process. Two different
>> products (different versions of the same product) would have different
>> product codes. So upgrade code is there to show that who are related.
>>
>> I did a debugging at bundle level and see that product codes are used in
>> dependencies.
>>
>> Hope this helps.
>>
>> -----Original Message-----
>> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On
>> Behalf Of Brian C Cooke
>> Sent: Friday, July 1, 2016 11:25 AM
>> To: wix-users at lists.wixtoolset.org
>> Subject: [wix-users] DetectRelatedMsiPackage
>>
>> I have a bundle with two packages which have different product codes but
>> the same upgrade code.  While installing a Major Upgrade in my custom BA,
>> the DetectRelatedMsiPackage event is getting triggered once for each
>> package but reporting the same product code both times.  e.g.
>>
>> e.ProductCode = <guid 1>, e.PackageId = package_name1
>>
>> and then
>>
>> e.ProductCode = <guid 1>, e.PackageId = package_name2
>>
>> Can anyone suggest why this is happening?  I would expect this event to
>> be triggered once with Product Code 1, and again with Product Code 2.  I am
>> on Wix 3.10.
>>
>> Thanks,
>> Brian
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.firegiant.com_&d=CwICAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=dIns6fQ--MkFJxuBFYmMeQ&m=MvVc2rM0ZyMxr5n9twRgtJC1ILCWRVDWW-eNvxufA4I&s=bo_qvUPGn1zygLOrSt8TdGOlD5KNzrp7x7VsqJUTBhQ&e=
>>
>
>