Wix heat.exe with project harvesting type

Question

I'm using the lastest version of Wix 3.5 and I'm trying to generate a fragment file using heat.exe. The command line is :

"%WIX%\bin\heat.exe" project "MyProj.csproj" -pog Binaries -pog Content -suid -directoryid 
INSTALLLOCATION -ag -template fragment -out "Files.wxs"

The prolem I'm having is that the assemblies my project is depending uppon are missing from the generated file. Is this the intended behaviour ? How can I add them ?

Should I use the dir harvesting type ?! How to remove *.pdb or *.vshost.exe then ?

I want to use it with CI Server (TeamCity)

edit: I tried -pog Satellites and doesn't work either

Solution 1

Unfortunately this is a known issue with WiX:

Heat doesn't harvest referenced assemblies

From the bug comments, it looks like support will be added in WiX 4.0.

Solution 2

I know this is an old question, but this thread might contain some ideas for possible solutions: How to add a whole directory or project output to WiX package

One of the tools mentioned, Paraffin 3.1, has various command line switches that should allow you to exclude the files that are not relevant. http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/06/28/paraffin3-1-new-and-improved.aspx

Comments

[Nitin Chhajer]

Hi, this is interesting stuff but doesn't answer the question : why doesn't heat.exe generate entries for the dependent assemblies with project harvesting

[Sergey Mirvoda]

@Catalin DICU. Yes I know. But I answered this way only because of out of luck with same task. After week of fighting with heat we decided to write some wxs files manually and some via generating wxi file with msbuild.

[Nitin Chhajer]

I ended up by using directory harvesting but it's puts the .pdb-s too. Not a big deal, I did't tried to filter them out using xslt; don't know if that would work

[David Keaveny]

I think I would have preferred they got this fixed before getting Burn up and running. Let's hope that v4 has a shorter gestation than v3.5/3.6...