GetLibrary simply adds the library to the other compiled wix code that light uses to link. There has to be some reference from somewhere for light to not throw out the fragment as unreferenced. That is the reason most compiler extensions use CreateWixSimpleReferenceRow to create references to appropriate things in the embedded library's Fragments.
-----Original Message----- From: Nick Ramirez [mailto:nickra...@hotmail.com] Sent: Monday, July 12, 2010 3:21 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Compiler extension - how to include a custom action? I've got an update. I've gotten my wixlib to show up in my MSI! The trick, for me, was to add a Property to the Fragment in the wixlib I was embedding and then use a PropertyRef to pull it in in my installer project. Pulling that in pulled in all the other stuff (including custom actions) from the wixlib (since it was all in the same fragment). Is this normal? GetLibrary doesn't do it alone? You have to use a reference element too? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Compiler-exten sion-how-to-include-a-custom-action-tp5271086p5285151.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 ------------------------------------------------------------------------------ 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
