Re: [WiX-users] Performing a Major Upgrade when only the Fourth Field of the Product Version Has Changed

ChaitanyaBhalerao wrote: > > > IncludeMinimum="yes" Minimum="1.0.0" > IncludeMaximum="no" > Maximum="$(var.ProductVersion)" OnlyDetect="no" MigrateFeatures ="yes" > IgnoreRemoveFailure ="no"/> > >

Re: [WiX-users] Performing a Major Upgrade when only the Fourth Field of the Product Version Has Changed

Matthew Sheets wrote: Using WiX v3, I would like to * Create a "major" upgrade installer, even when only the fourth field of the Product Version has changed "Doctor, it hurts when I do this." You know the rest. It might be possible to make it work but you're fighting Windows Insta

Re: [WiX-users] Performing a Major Upgrade when only the Fourth Field of the Product Version Has Changed

That design limitation is a function of FindRelatedProducts which processes the upgrade rule and sets the ; delimited list of ProductCodes in the ActionProperty.RemoveExistingProducts doesn't really care about this business rule since it's just processing the list. You could author and

[WiX-users] Performing a Major Upgrade when only the Fourth Field of the Product Version Has Changed

Using WiX v3, I would like to * Create a "major" upgrade installer, even when only the fourth field of the Product Version has changed * Skip installation if a newer version is installed (again, even if only the fourth field of the Product Version has changed) For example, if the n