[wix-users] File downgrades in 3rd party components

[Christopher Painter]

Do you have a bootstrapper / chainer?  One approach would be to compartmentalize those files into a micropackage (MSI)  with AMUS versioning rules rather then OMUS rules. I would only do these files are completely self contained with zero risk of DLL hell / component rule pain.


 Then your main MSI could use OMUS and the bootstrapper can make sure both both packages are installed as part of bundle servicing.


________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Joel Budreau <joel.budreau at gmail.com>
Sent: Tuesday, May 9, 2017 4:14 PM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] File downgrades in 3rd party components

The impression that I get is that the solution here is to take the
downgraded file and change it into a companion-file as a part of a
different component (in the same directory).

I'd be interested to hear if another solution is better...

On Tue, May 9, 2017 at 11:10 AM, Joel Budreau <joel.budreau at gmail.com>
wrote:

> I've got a product that packages java files directly into my MSI. Once in
> a while, a java update will introduce a file or two that have downgraded in
> file version from a previous release. This causes those java files to end
> up missing from the system after running a major upgrade of my product. How
> should this situation be addressed?
>
> Thanks,
> Joel
>

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
WiX Support | WiX Experts and Resources from FireGiant<http://www.firegiant.com/>
www.firegiant.com
WiX Support | Installation, Development, Deployment | WiX Experts and Resources from FireGiant