Yeah, that's a bug in the engine. Superseded needs to be treated like
Present but currently treated like Absent.
On Tue, Feb 28, 2012 at 8:21 AM, Vadym Verba wrote:
> Good day (I hope!).
>
>
>
> I think we found some workaround for updating old bundle, but now we have
> another problem with patc
Good day (I hope!).
I think we found some workaround for updating old bundle, but now we have
another problem with patch implementing via RelatedBundle element. I did as
you said:
Added to main bundle, and
to patch bundle. Main bundle does
detect related patch and maintain it accordingly, bu
Hey, I'm just glad you confirmed those things are all behaving correctly.
We're getting very close with Burn. I'm quite excited.
On Fri, Feb 24, 2012 at 5:58 AM, Vadym Verba wrote:
> I double checked everything again...
>
> 1. You were right ) it does show up in ARP "Updates"
>
> 2.
I double checked everything again...
1. You were right ) it does show up in ARP "Updates"
2. You were right ) There is also the same key in CurrentUser
3. I was wrong ) It was some kind of resource conflict: new file in
patched package had the same component name as another fil
1. I hope the Patch Bundle shows up in "Installed Updates" in ARP.
2. Are you sure that isn't just the backing key for a more well known name?
I would be surprised if that is where the key is requested from.
3. Would need the Burn logs to diagnose the prompt for source issue.It is
possible there
Hey there.
Thx for your reply. I really looked forward to). I read on Hearth's blog
about Patching and Add-ons, and tried some. It does work as described). So
thx for that to! One thing I noticed is that "Patch" bundle is not displayed
in ARP, so there are no normal ways to delete it. Is it by des
Interesting. I was just going to say that in the latest build we updated
the patch detection to be able to target the UpgradeCode of a Bundle.
Otherwise, the only way to use the patch RelatedBundle was to add a
RelatedBundle of type "detect" to the original Bundle. Of course, if you've
already ship
Hey again.
I know I'm probably the most annoying person, but we have a problem with
released bundle here and we are out of options how to update/patch it
properly. I think I understood how BA should handle detected patches, but it
has been already released.
Please tell me is there any possibility t
Here is what I ended up with:
BundleHotfix.wxs:
Btw I don't know another way to get original bundle GUID rather then look at
its installation log file and find location where it is cached to
(C:\ProgramData\PachakeCache\{ORIGINAL-BUNDLE-GUID}\.ex
On 25-Jan-12 04:15, Vadym Verba wrote:
> Here is usecase: I have old v1.0 bundle installed and new "patch" bundle with
> patches only (totally new bundle with new upgrade code or with the same
> one?).
You'll have to do some additional work to associate the bundles. I
haven't done it, so I'm not
indicate that bundle is a patch for already existing one.
--
Date: Tue, 24 Jan 2012 12:15:26 -0500
From: Bob Arnson
Subject: Re: [WiX-users] Burn: patch for bundle
To: wix-users@lists.sourceforge.net
Message-ID: <4f1ee72e.1070...@joyofsetup.com>
Content-Type:
On 24-Jan-12 10:02, Vadym Verba wrote:
> I have a small but a very vital question: how to patch bundle?
Build a new bundle that contains the patches, either by themselves or
with the original packages.
--
sig://boB
http://joyofsetup.com/
Hello.
I have a small but a very vital question: how to patch bundle? I mean, let
say I have some bundle of 1.0 version with few products inside of 1.0 version
as well. If I just install patches for products themselves they will be of
1.1 version and if I launch bundle it will detect downgrade, be
13 matches
Mail list logo
