Bugs item #1717558, was opened at 2007-05-11 23:30
Message generated for change (Comment added) made by tpaxatb
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1717558&group_id=105970
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: light
Group: None
Status: Open
Resolution: None
>Priority: 7
Private: No
Submitted By: Doug S (tpaxatb)
Assigned to: Nobody/Anonymous (nobody)
Summary: Native assembly manifest reference fails
Initial Comment:
When building a native assembly, in order to properly generate all the
MsiAssembly tables, the files in the assembly's component must be listed in the
order:
<Component Id="x86Assembly" Guid="19715da1-4604-4d14-a60a-4e5b1b6e71b7">
<File Id="Dllx86" Assembly="win32" Name="ImageProcessing.Quality.dll"
KeyPath="yes" AssemblyManifest="Manifestx86" />
<File Id="Catalogx86" Name="ImageProcessing.Quality.dll.cat" />
<File Id="Manifestx86" Name="ImageProcessing.Quality.dll.manifest" />
</Component>
Otherwise, a LGHT0104 error occurs because the manifest parser reads the
incorrect file.
It took a lot of trial and error to figure this out. Note that suppressing the
MsiAssembly or MsiAssemblyName table generation causes a succeed. In addition,
when the AssemblyManifest attribute is removed from the key file's element, the
MsiAssemblyName table is still generated correctly, seemingly reading the
manifest file even though I didn't tell WiX which file to use.
----------------------------------------------------------------------
>Comment By: Doug S (tpaxatb)
Date: 2007-05-12 09:54
Message:
Logged In: YES
user_id=1342505
Originator: YES
Quick update, it seems that light is ignoring the AssemblyManifest
attribute and only finding the last filerow speficied in the table. I have
3 native assemblies in the project and they all use the last manifest in
the table. In Binder.cs, there seems to be a comment to reveiew the logic.
The only workaround I have found is to suppress the generation of the
MsiAssemblyName table and manually create assembly references (ummm, the
project has 43 assemblies, not very feasible!)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1717558&group_id=105970
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
