<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Cannot run LibreOffice, api-ms-win-crt-runtime-l1-1-0.dll is missing (for local solution see comment 7)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108580">bug 108580</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>d.ostrovsky@gmx.de
</td>
</tr>
<tr>
<td style="text-align:right;">See Also</td>
<td>
</td>
<td>https://bugs.documentfoundation.org/show_bug.cgi?id=105311
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Cannot run LibreOffice, api-ms-win-crt-runtime-l1-1-0.dll is missing (for local solution see comment 7)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108580#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Cannot run LibreOffice, api-ms-win-crt-runtime-l1-1-0.dll is missing (for local solution see comment 7)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108580">bug 108580</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>As documentation states, [1] if a directory name *starts with* one of
predefined SystemFolder properties, a CustomAction type 51 is generated for it.
"It does not verify that the directory name exactly equals the directory
property. Any directory beginning with one of these standard folder names gets
a type 51 custom action, even if the rest of the name is not a GUID."
Our fix for <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Windows Installer: C-Runtime DLLs installed in wrong directory"
href="show_bug.cgi?id=105311">bug 105311</a> follows this description literally. But my concern is if
we are victims of another MS documentation flaw. I mean, the passage "The
tables in the merge module must reference the location of a child directory of
TARGETDIR, *or another directory in the merge module's tree*" in the mentioned
documentation page (emphasis mine).
The C-Runtime merge module has two directories in it, named
SystemFolder.E281B893_10D7_34CE_BB0E_B69D88E154A5
and
SystemFolder_x86_VC.E281B893_10D7_34CE_BB0E_B69D88E154A5
The former has its parent set to TARGETDIR, and the latter has its parent set
to former (SystemFolder.E281B893_10D7_34CE_BB0E_B69D88E154A5). I.e., they form
a hierarchy (though the latter doesn't define any subdirectory).
But we generate two custom actions for both of them, because they both do begin
with "SystemFolder". Thus, we may break the hierarchy (that's my guess).
Intuitively, this shouldn't break things, as we still point both to a proper
location, but who knows.
Could it be that MS documentation must be read as "if directory name *before
dot* is equal to one of pre-defined SystemFolder properties, ..."?
Adding David Ostrovsky (the author of fix for <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Windows Installer: C-Runtime DLLs installed in wrong directory"
href="show_bug.cgi?id=105311">bug 105311</a>, and expert in this
area) to CC list.
[1] <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa367787">https://msdn.microsoft.com/en-us/library/windows/desktop/aa367787</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>