No problem. This is what we do for our customers every day at FireGiant 
(although FireGiant answers are far more detailed than the 1-2 sentences I have 
time to write here).

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


-----Original Message-----
From: Lukas Rieger [mailto:lrie...@nemetschek-engineering.at] 
Sent: Friday, April 24, 2015 11:33 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Major upgrade: a few files are not installed

I thought it treated files like MSIs and only compared the first three digits, 
so I glanced over the version number. Comparing them again, OLD > NEW.

File Table |File                                            | Component_   
                             | FileName    | FileSize | Version
-----------|------------------------------------------------------------
-----------|------------------------------------------------------------
-----------|--------------------
old MSI    |fileEcMWtDjRdBXxvVHY.WvW_XXJI4GZcq5iAszC_F3KIwk | 
Cj9pc73bMjDSVVGUqS81_nPSltSFuUEweshtzct2AHi4 | bftlang.dll | 118784   | 
2004.553.4453.1067
new MSI    |fileYXlC3cFPRwh6qrJ5u..Ll052XUiMylAmA6a4BwMlz_o | 
CZJsalkL4nX.r6JS5xXH3pjmr9mY1AO4CITmUEHjP82I | bftlang.dll | 118784   | 
2004.553.4453.1064

Component Table |Component                                    | 
ComponentId                            | KeyPath
----------------|-------------------------------------------------------
----------------|-------------------------------------------------------
----------------|-------------------------
old MSI         |Cj9pc73bMjDSVVGUqS81_nPSltSFuUEweshtzct2AHi4 | 
{C45097D5-E359-48B5-9F85-AB5EC81D62BF} |
filepcu3NI3UMnsXucCthGSqTSHMvUoyVuyQHRbEXnUVii0
new MSI         |CZJsalkL4nX.r6JS5xXH3pjmr9mY1AO4CITmUEHjP82I | 
{8B97BC16-7D4D-45CD-A3E3-903C60868202} | 
fileYXlC3cFPRwh6qrJ5u..Ll052XUiMylAmA6a4BwMlz_o


MSI (s) (88:A0) [20:12:50:115]: Disallowing installation of component: 
{8B97BC16-7D4D-45CD-A3E3-903C60868202} since the same component with higher 
versioned keyfile exists

Now that log entry finally makes sense...
*head->table*
Thank you!

So I guess the question becomes how to best downgrade a file during a major 
upgrade...
We have no shared components or merge modules, so we always want to put exactly 
the version in the msi on disk, even if that means downgrading.
At least according to this (
http://stackoverflow.com/questions/4227456/windows-installer-deletes-versioned-file-during-product-upgrade-instead-of-down?rq=1
) post, scheduling before Costing should work, so I will try that.

Thank you again,
Lukas

------------------------------------------------------------------------------
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

Reply via email to