[wix-users] Question on Minor upgrade

[Christopher Painter]

Amen.  There are very specific use cases for it.  I remember about 8 years ago I flew Blair Mur out to Austin to interview for our team.  He gave an example from Microsoft that demonstrated some real $$$$ value.  However, IMHO,  the vast majority will never need it.


I will admit that I came to this conclusion prior to becoming a patching wizard.  I do come across customers from time to time that need a patching wizard.  Shoot me your details if you'd like referral work.


________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Edwin Castro via wix-users <wix-users at lists.wixtoolset.org>
Sent: Thursday, November 16, 2017 5:19 PM
To: WiX Toolset Users Mailing List
Cc: Edwin Castro
Subject: Re: [wix-users] Question on Minor upgrade

IMHO, the biggest issue with patches in general, beyond all the technical
difficulties, is that you're allowing untested combinations of component
versions on the field which is completely dependent on which patches have
been installed by customers. The more patches that are delivered to
customers, the higher the probability that the specific version combination
at the customer site has never been tested! On the other hand, major
upgrades ensure a known, tested combination of component versions at
customer sites. The demand for patches is, generally speaking, an
antiquated solution to a bandwidth problem. Folks that demand patches
usually do not understand why patches were a good thing to begin with.

--
Edwin G. Castro


On Thu, Nov 16, 2017 at 1:40 PM, John Zajac via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> My advice (proven by taking Christopher's advice a long time ago): ditch
> the minor upgrade. Or at make sure you're getting value out them. IMHO,
> they are more problematic than useful, and this issue you're encountering
> is just one of a myriad of issues you'll likely encounter.
>
> Usually some internal or external customers think patches and such are
> 'simpler', which is exactly the opposite in reality.
>
> And yes even for very large installs (thousands of files), a well defined
> Major Upgrade MSI is far more flexible and reliable.
>
> I did get MSP patching with WiX Toolset to work great - fully automated
> too. However it still comes with a high maintenance cost (and in my opinion
> is a huge waste of money).
>
> On Thu, Nov 16, 2017 at 9:24 AM, Hoover, Jacob via wix-users <
> wix-users at lists.wixtoolset.org> wrote:
>
> > https://msdn.microsoft.com/en-us/library/windows/desktop/
> > aa368364%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
> >
> > New components are ok but you cannot remove a component from an existing
> > feature in a minor upgrade (unless you are going to restrict to 4.5+ and
> do
> > extra work).
> >
> > -----Original Message-----
> > From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On
> Behalf
> > Of Ven H via wix-users
> > Sent: Thursday, November 16, 2017 1:36 AM
> > To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> > Cc: Ven H <venh.123 at gmail.com>
> > Subject: [wix-users] Question on Minor upgrade
> >
> > Can a new component (say a file or a registry key) installation or
> removal
> > of an existing component be part of Minor Upgrade?
> >
> > Regards,
> > Venkatesh
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
>
>
>
> --
> -John
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>

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