I just had to do this for one of our projects.
I temporarily changed the file being downgraded from being its own component to
being a dependency of another component. After we did our release I put the
component rules back so it is unique in future changes.
Original Component section:
<Component Id="cmpBiggerFile" Guid="{AnyGUID}">
<File Id="fil1" KeyPath="yes" Source=" \$(var.AppSource)\FileN1.ocx" />
</Component>
The temp code likes like this
<Component Id="cmpTempParent" Guid="{parentGUID}">
<File Id="filTempP" KeyPath="yes" Source="
$(var.AppSource)\Parent.dll" />
<File Id=" filF1 " KeyPath="no" CompanionFile=" filTempP " Source="
\$(var.AppSource)\FileN1.ocx"/>
</Component>
The code forces the file you are downgrading to be removed and replaced on
every install. It's not a good long term answer but it was good enough to 1
version of upgrade
-----Original Message-----
From: David Watson [mailto:dwat...@sdl.com]
Sent: Thursday, May 21, 2015 7:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Overwrite a file with a higher Version
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
