?
>
> Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 21 September 2012 18:23
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
>
> Heh, heh, yeah, you
: Re: [WiX-users] Bootstrapper Upgrade Detection
Heh, heh, yeah, you'll go into an infinite loop if the two equal bundles keep
upgrading each other. I bet you ended up with thousands of burn processes
running trying to upgrade each other. Heh.
You probably need to throw in the "re
; > From: Rob Mensching [mailto:r...@robmensching.com]
> > Sent: 17 September 2012 18:39
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
> >
> > You should be able to request ABSENT for the OnPl
k correct?
>
> Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 17 September 2012 18:39
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
>
> You should be able t
s Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
You should be able to request ABSENT for the OnPlanRelatedBundle() of the
bundle that has the same version. The default is NONE so it stays.
On Mon, Sep 17, 2012 at 10:03 AM, Neil Sleightholm wrote:
> >> The
ould be wrong.
> > >> > > > On Sep 17, 2012 4:33 AM, "Neil Sleightholm" >
> > >> > wrote:
> > >> > > >
> > >> > > > > Do you mean multiple entries from your burn package or the
> msi?
gt; > > > > >Does this mean I should remove the AllowSameVersions from the
> >> > > > MajorUpgrade
> >> > > > > >tag also? Right now I still get multiple entries with different
> >> > > versions
> >> > > > > >but I still h
ries with different
>> > > versions
>> > > > > >but I still have the flag there.
>> > > > > >
>> > > > > >Greg Beaty
>> > > > > >greg.bea...@gmail.com
>> > > > > >
>> > > &g
ty
> > > > > >greg.bea...@gmail.com
> > > > > >
> > > > > >
> > > > > >On Sun, Sep 16, 2012 at 12:41 PM, Neil Sleightholm
> > > > > >wrote:
> > > > > >
> > > > > >> I ha
Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 17 September 2012 17:28
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
>
> The default upgrade logic in the
gt; I had this issue when I had done some same version installs and
> then
> > > > >> started changing the version; the cause was multiple entries in
> ARP.
> > > It
> > > > >> might we worth checking this, I found if I removed all the
> ver
ssue when I had done some same version installs and then
> > > >> started changing the version; the cause was multiple entries in ARP.
> > It
> > > >> might we worth checking this, I found if I removed all the versions
> > then
> > > >> the upgrades started worki
l it is baked in to the Engine and I couldn't find any way to
override it.
Neil
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 17 September 2012 17:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper Upgrade De
started changing the version; the cause was multiple entries in ARP.
> It
> > >> might we worth checking this, I found if I removed all the versions
> then
> > >> the upgrades started working.
> > >>
> > >> Neil
> > >>
> &
t;>
> >> Neil
> >>
> >> -Original Message-
> >> From: Gregory Beaty [mailto:greg.bea...@gmail.com]
> >> Sent: 16 September 2012 17:36
> >> To: General discussion for Windows Installer XML toolset.
> >> Subject: Re: [WiX-users
if I removed all the versions then
>> the upgrades started working.
>>
>> Neil
>>
>> -Original Message-
>> From: Gregory Beaty [mailto:greg.bea...@gmail.com]
>> Sent: 16 September 2012 17:36
>> To: General discussion for Windows Installer XML
--
> From: Gregory Beaty [mailto:greg.bea...@gmail.com]
> Sent: 16 September 2012 17:36
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
>
> Even my different version upgrades don't remove the previous installed
&g
Beaty [mailto:greg.bea...@gmail.com]
Sent: 16 September 2012 17:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
Even my different version upgrades don't remove the previous installed version.
I seem to have problems uninstall
t;> -Original Message-
>> From: Gregory Beaty [mailto:greg.bea...@gmail.com]
>> Sent: 16 September 2012 15:27
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
>>
>> 1. Wix supports same ve
ure request
> but can't find it now.
>
> Neil
>
> -Original Message-
> From: Gregory Beaty [mailto:greg.bea...@gmail.com]
> Sent: 16 September 2012 15:27
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bootstrapper Upgrade
For info; this is the bug report http://sourceforge.net/p/wix/bugs/3065/
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 16 September 2012 17:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
2 15:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper Upgrade Detection
1. Wix supports same version major upgrades that are the same version using the
SameVersion flag. Why isn't Burn using this as well, or is there a way to turn
it on?
Greg
Also I just re-ran the upgrade and the versions are different, but it still
places two different versions into the Add/Remove programs list.
Greg Beaty
greg.bea...@gmail.com
On Sun, Sep 16, 2012 at 10:26 AM, Gregory Beaty wrote:
> 1. Wix supports same version major upgrades that are the same ve
1. Wix supports same version major upgrades that are the same version using
the SameVersion flag. Why isn't Burn using this as well, or is there a way
to turn it on?
Greg Beaty
greg.bea...@gmail.com
On Fri, Sep 14, 2012 at 1:01 AM, Rob Mensching wrote:
> 1. Bundles with the same UpgradeCode h
1. Bundles with the same UpgradeCode have an upgrade relationship.The
higher version removes the lower version. Same versions but built at
different times can end up in the situation you describe.
2. There should be very few differences between gettinga BA written for
NETFX 3.5 vs. 4.0. Actually
Sorry for the double post.
Greg Beaty
greg.bea...@gmail.com
On Fri, Sep 14, 2012 at 12:19 AM, Gregory Beaty wrote:
> Thanks Rob.
>
> I do have another issue. How do I disable the ability for the BA to
> install multiple versions of my application? It seems that during an
> upgrade it installs a
Thanks Rob.
I do have another issue. How do I disable the ability for the BA to install
multiple versions of my application? It seems that during an upgrade it
installs an entirely new app and there ends up being multiple entries in
Add/Remove programs.
Are there any examples of a managed BA for
Thanks Rob.
I do have another issue. How do I disable the ability for the BA to install
multiple versions of my application? It seems that during an upgrade it
installs an entirely new app and there ends up being multiple entries in
Add/Remove programs.
Are there any examples of a managed BA for
The RelatedOption.None is how you know. In WiX v3.7 you also get the
relation type which will further inform you that you have a related Bundle
that is an upgrade but it's operation is None (i.e not upgrade and not
downgrade).
On Thu, Sep 13, 2012 at 4:54 AM, Gregory Beaty wrote:
> Hello,
>
> My
Hello,
My WiX MSI package allows same version upgrades with: .
However when using this with my Manager Bootstrapper Application I never
get the RelatedOperation of a MinorUpgrade or MajorUpgrade in the
DetectRelatedBundle event. I only get RelatedOption.None. The process
indeed upgrades the previ
30 matches
Mail list logo
