Re: [WiX-users] Heat.exe not including all references/dependencies

2013-06-24 Thread Tom -
necessary file. Best Regards, Tom > Date: Sat, 22 Jun 2013 14:34:44 -0400 > From: gorley.phili...@gmail.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Heat.exe not including all references/dependencies > > You could create a separate configuration, say Custom

Re: [WiX-users] Heat.exe not including all references/dependencies

2013-06-22 Thread Blair Murri
er changing a component's guid). Blair Murri > Date: Sat, 22 Jun 2013 14:34:44 -0400 > From: gorley.phili...@gmail.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Heat.exe not including all references/dependencies > > You could create a separate confi

Re: [WiX-users] Heat.exe not including all references/dependencies

2013-06-22 Thread Philippe Gorley
You could create a separate configuration, say Custom|AnyCPU, for your solution, where all of your projects' output paths are set to the same folder, along with all assemblies having CopyLocal set to true, so you can just run Heat on that directory to grab everything. You would do this by addin

[WiX-users] Heat.exe not including all references/dependencies

2013-06-22 Thread Tom -
This is a follow-up to my previous conundrum of all needed assemblies not getting included in my setup-package. The answer seems simpler than I thought. Previous setup projects in VS.NET 2010 was obviously kind enough to detect and include all references. Setting Heat.exe to a single output dire