Ah. I haven't looked at Burn. Sorry. Hopefully someone else has the answer
to that one.
Rob
On 04/07/2011 12:13, Alexander Krivács Schrøder wrote:
> Hi Rob.
>
> I probably should have mentioned that the bootstrapper we're using is WiX's
> burn, and the managed GUI we're making is for it. The BootstrapperApplication
> class has an event called DetectPackageComplete. In this event, one gets the
> following EventArgs class:
>
> public class DetectPackageCompleteEventArgs
> {
> public string PackageId { get; }
> public PackageState State { get; }
> }
>
> It is this PackageState I am talking about; it doesn't get set to what we
> expect, as I mentioned in my first mail.
>
> Best regards
>
> ALEXANDER K. SCHRØDER
>
> -----Original Message-----
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: 4. juli 2011 11:25
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Bootstrapper upgrade code detection
>
> If you were using native code, then you'd want MsiEnumRelatedProducts(). A
> Google search provides a bunch of links with info on how to call it from C#.
> I don't know if you're using C# or VB, but a bit of searching around that
> function name should get you there.
>
> Rob
>
> On 04/07/2011 09:52, Alexander Krivács Schrøder wrote:
>> Hey.
>>
>> According to the Windows Installer specifications, we change the Product
>> Code of our product with every release (We just use<Product Id="*" ... />)
>> and we keep the Upgrade Code the same. That way, when the individual MSIs
>> are run, if any previous versions exist, they are first uninstalled.
>>
>> At the moment, we're making a bootstrapper for our products, and in this
>> process, we're also making a custom managed GUI. It detects if a product is
>> already installed (its PackageState is reported as PackageState.Present) or
>> not installed (PackageState.Absent). However, if a product is installed, but
>> the bootstrapper contains a newer version of the product, it is reported as
>> PackageState.Absent, not PackageState.Superseded, like one would expect.
>>
>> Is there anything in particular we need to do in order to get this upgrade
>> detection mechanism to work?
>>
>> Best regards
>>
>> ALEXANDER K. SCHRØDER
>>
>> ----------------------------------------------------------------------
>> -------- All of the data generated in your IT infrastructure is
>> seriously valuable.
>> Why? It contains a definitive record of application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
