[wix-users] WiX Patch Bundle Question

[Rob Mensching]

You could mark your Bundle and an "update" then it gets tucked away in the installed updates. Avoids clutter.

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Christopher Painter
Sent: Friday, February 24, 2017 2:31 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WiX Patch Bundle Question

I could see that as a best practice in initial development.  I do something similar with Services in that I don't  set them to start until they have proven reliable.   But for end users I wouldn't want to let them see the micropackages and have a chance to break them.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Douglas, Keith (STATCAN)
Sent: Friday, February 24, 2017 7:51 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WiX Patch Bundle Question

It is a bit cluttered, but I do always flag the packages in my bundle as visible in P&F. It helps in situations like this.


Keith Douglas

Programmer Analyst, Information Technology Operations Divison Statistics Canada / Government of Canada keith.douglas at canada.ca / 613-854-5589

Programmeur Analyste, Division des opérations des technologies de l'information Statistiques Canada / Gouvernement du Canada keith.douglas at canada.ca / 613-854-5589

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Christopher Painter
Sent: February-23-17 6:40 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WiX Patch Bundle Question

Oh fudge....  my rapid prototype was only changing the version in the 4th field and the major upgrade was failing.  I couldn't "see" this because Burn owned the Programs and Features entry.


Doh!  I know better that that.....   Hopefully this helps someone some day.

-----Original Message-----
From: Christopher Painter
Sent: Thursday, February 23, 2017 5:37 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: RE: Re: [wix-users] WiX Patch Bundle Question

Ok, I'm losing it. I retested and saw the original behavior.  I'm currently reading burn log files for the first time and seeing a few things that don't make sense to me.


Because my MSIs are authored using major upgrade and detect newer version I'd assume that Burn would have to uninstall  the newer version and then reinstall the old version.  But it seems to be removing the new one and leaving the components behind and then when the old one is installed it's   logged as already installed and reconfiguring.   Because a newer version of my file is installed  costing decides theres nothing to do.

So technically the older MSI is now installed but I have newer versions of my files.

What am I missing?


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Christopher Painter
Sent: Thursday, February 23, 2017 5:02 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WiX Patch Bundle Question

Thanks for indicating that it *should* work.  It gave me an idea on what might be wrong and give it one more try.  I hadn't set the Cached attribute on the MsiPackage elements.  I'm guessing if it's not cached it can't repair the bundle and it doesn't tell you that either.   Adding the attribute caused the patch removal to reinstall the original packages.

Thanks a bundle!   (I'm sorry, had to do it.)

Chris

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of robert_yang at agilent.com
Sent: Thursday, February 23, 2017 3:31 PM
To: wix-users at lists.wixtoolset.org
Subject: Re: [wix-users] WiX Patch Bundle Question

"Pardon if this is a simple question, I haven't done much with Burn.

Hunting around the internet (and getting help from a 2013 version of myself... don't even remember asking that question LOL )  I managed to put together a v1.0 bundle and a v1.1 patch bundle prototype where the patch bundle can't be installed unless the base bundle is installed.  Pretty good so far except I can't figure out a few issues:


1)      Removing the v1.1 patch bundle doesn't revert MsiPackage A from 1.1 back to 1.0.  Running repair on the 1.0 bundle doesn't downgrade the package to 1.0 either.   How should I approach this?"

Hmm, we don't have this problem.  Perhaps post the code of your patch bundle ?  Uninstalling a patch bundle "should" result in the patch being removed and the original bundle being repaired.  I say "should" because the addition of the second step is the way it has worked since 3.9.  I had to write a custom BA (really just the std BA with a couple hacks) to get the 3.8 behavior back.

Our patches are basically .msp's with a bundle.

-Rob


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/