Heat output generates CNDL0047 in candle

[wixbot]

When i heat a tybelib resource, the output seems not be 3.5 "conform" and therefore candle exits with an error.

error CNDL0047 : The TypeLib element is non-advertised and therefore requires a parent File element.

Some additional information provided in this bug report (attachments):

• Result "Heat"
• How it should look like (original msi)

Originally opened by dilorenzo1987 from http://sourceforge.net/p/wix/bugs/2758/

[wixbot]

Yet it is a duplicate. but pls have a look onto the screenshot. in my opinion its still an error of heat:

it doesnt recognize the second typelib registration of the ocx (If you move them under the "file" tag it works)

[wixbot]

Duplicate of 3043870

[wixbot]

How it should look like (original msi)

[wixbot]

The specific problem here is that TypeLib harvesting doesn't correctly deal with:

• Populating the TypeLib ResourceId attribute from the Win32 key.
• The Win64 tree isn't examined at all in fact.

Fabio was trying to harvest Flash11e.ocx.

The Win64 issue will show up when you try and harvest the 64bit Flash ActiveX control (Flash64_11_1_102.ocx) or its current equivalent.

[wixbot]

Originally changed by barnson Area changed from heat to ` Releasechanged fromfuturetov3.x`

[wixbot]

Originally changed by bmurri AssignedTo set to wixsupport

[ostengaard]

Any timeline for when this might get solved?

Thanks

[robmen]

The bug is open and unassigned. In other words it is waiting for someone to investigate, propose and develop a fix. It'll hang out in the WiX v3.x bucket until then.

[zdavidsen]

I'm currently running into this and at least in my case, it seems to be related to building from a .sln file. Building from within visual studio (2019), full solution or just the .wixproj, produces the orphaned TypeLib, same results when invoking msbuild on the .sln file.
Invoking msbuild on the .wixproj file produces the correct output, and adding the following snippet to the .wixproj fixes building the solution/project from visual studio and from msbuild

  <PropertyGroup>
    <RunWixToolsOutOfProc>true</RunWixToolsOutOfProc>
  </PropertyGroup>

[BYugandhar]

i have tried using above snippet of code, same issue observed using MSBuild also, any help for the same.

[BYugandhar]

i am still facing same issue can any one suggest is there any alternate solution for nested typelib issue ?

[mobigliani]

I use the following XSLT to restructure single File into working code:

   <!-- Put TypeLib node under File -->
   <xsl:template match="wix:File">
      <xsl:copy>
         <xsl:apply-templates select="@*" />
         <xsl:apply-templates select="node()" />
         <TypeLib>
            <xsl:apply-templates select="../wix:TypeLib/@*" />
            <xsl:attribute name="Language">
               <xsl:value-of select="0" />
            </xsl:attribute>
            <xsl:copy-of select="../wix:TypeLib/node()" />
         </TypeLib>
      </xsl:copy>
   </xsl:template>

   <!-- Remove TypeLib node from under Component -->
   <xsl:template match="//wix:Component/wix:TypeLib" />