Thanks Rob. I'd love to contribute. Where do you need more eyes?
As for the compiler extension, I'm back to where I was. I haven't been able
to get Candle to recognize the embedded wixlib in my compiler extension.
Experimenting with several ideas, I've added the <Link> element to my build
script, thinking that might be it, but it didn't solve the problem. I have
this in my extension's csproj file now:
<ItemGroup>
<EmbeddedResource Include="..\Output\CustomExtensionLibrary.wixlib">
<Link>Library\CustomExtensionLibrary.wixlib</Link>
</EmbeddedResource>
</ItemGroup>
If I use Reflector on my built assembly, I see that the wixlib, xsd and xml
file are embedded. I used the -bf flag on the wixlib so that it binds the
data into it. It's so strange. When I use my extension, the custom table is
added to the MSI, but nothing from the wixlib (CustomAction table, Binary
table).
I wonder if there's something I'm missing in the csproj file for the
extension? I see that the examples use "WixBuild.Common.targets". Do I need
to import this too and add extra MSBuild elements?
I'm still not quite sure how to debug Candle. Does anyone have experience
doing it?
I'm using WiX 3.0 in Visual Studio 2008. Thanks for the help everyone.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Compiler-extension-how-to-include-a-custom-action-tp5271086p5285053.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
