In regard to using HarvestDirectory, look at the folder obj\$Configuration and review the wxs file produced by the HarvestDirectory. Does it include all of the files that you are trying to harvest from the folder ..\PRISMContingencyService\bin\$(Configuration)\ ? Or are you installing some of the files as third-party redistributables using a bundle chain (which goes to Phil's suggestion)? In my use of HarvestDirectory I had to remove the trailing backslash.
I would suggest commenting out the ServiceInstall and ServiceConfig, and focus on creating a setup package which deploys all of the files needed to the target system. Once that level of functionality is working you can uninstall that instance, and then add the service elements back in. You will probably want to create a transform.xslt to strip out the service file, and then author it and the service elements separate from the harvested output. I do not have an example handy, but there are many google results related to using xslt to strip a file from a wxs output. I would enable verbose build logging and review the information related to HarvestDirectory. If using VS look at Tools\options. I suspect that the relative path is not being resolved, but reviewing the output wxs file and the verbose build log will tell the story. If that does not clarify a harvesting issue, then I would create a batch file to call heat directly for the purpose of debugging your approach to using heat.exe. Another thing that I noticed in your first post is that you defined a <Component Id="Component.ServiceComponent"> but did not include the reference in your feature: <ComponentGroupRef Id="Component.ServiceComponent"/> Harvesting can be tricky, and can create complex maintenance ramifications. There have been recent posts with good information on the concerns with using harvesting in production. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-service-installation-to-wix-installer-tp7598681p7598704.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
