For what it is worth, I would look at using the HarvestProjects Target rather than the Task. I have not harvested projects, but I do harvest directories. I started using a batch file, then the HeatDirectory Task, and now I use HarvestDirectory Target, as described here <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Automatically-harvest-files-in-VS-2013-td7597592.html#a7597597> . Using the Target provides much better integration than using the Task (or batch file). I believe that using HarvestProjects will have some similarity to HarvestDirectory, however by default HarvestProjects is disabled, so look at the chm as to how to enable it with: <PropertyGroup> <EnableProjectHarvesting>True</EnableProjectHarvesting> </PropertyGroup>
I have also heard others discuss the fact that when harvesting projects, they needed to create transforms to avoid harvesting certain files from the output folders. And they pointed out that another approach was to add code to each project to copy only the desired output files to a common output folder tree, and then use HarvestDirectory to harvest that folder. Not a direct answer to your question, but I hope it helps. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Looking-for-working-HeatProject-Example-tp7600163p7600165.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
