This problem is solved now. For the record, I used Nick's CopyResource idea and it worked. For anyone else who tries this solution, there are two additional things worth pointing out:
1) Copying a resource in this way can leave it behind on the target computer in the temporary installation folder when the installer is finished. I had to add a custom action to delete the DLL when the installer was finished. 2) Initially I tried copying the DLL once in a separate custom action, but I was finding that it was no longer there when I tried doing another custom action that needed it. Not sure why this was happening, but I worked around it by discarding the separate custom action, and instead I now do the DLL copy in each custom action that uses the old DLL. It means that the copy might happen a few times during installation, but it works. I did not try using JEDI like Bob suggested, but I read a bit on it and it looks like a promising approach. If there was time in the schedule I think this would be the right way to go. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Including-third-party-DLLs-for-installer-to-use-tp7585415p7585440.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
