[wix-users] Adding Output of a Reference Project
rob at firegiant.com
Tue Jun 8 09:17:41 PDT 2021
Not an answer: but project reference harvesting is way more complicated than it seems like it should be. At FireGiant we spent a lot of time working on advanced harvesting solution (https://www.firegiant.com/wix/wep-documentation/harvesting/).
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Bryan Dam via wix-users
Sent: Friday, May 28, 2021 1:01 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Bryan Dam <bryand at recastsoftware.com>
Subject: [wix-users] Adding Output of a Reference Project
I have multiple EXEs that need to be installed as well as called via deferred custom action. Their projects are in the same solution as the WiX project and each contain a whole long list of dependencies (NuGet packages). What I'm having trouble doing is automatically capturing the output of the EXE projects. I can manually build the EXEs and copy everything into an existing supporting file directory we harvest with HeatDirectory task. That works but ideally I'd like to be able to build the whole solution in one go.
I've tried using project harvesting but while that grabs the actual EXEs themselves it doesn't grab their dependencies (a known issue).
So I'm trying to use HeatDirectory: Directory="$(ProjectDir)\..\MyReferencedProject\bin\$(Configuration)". This works and generates the output file but the source all point to SourceDir as the root and the build complains that it can't find the files. With the supporting files we use a pre-processor variable but in this case I want to refer directly to a relative path.
Is there a way to get the HeatDirectory task to generate relative paths to the source files? Or maybe a better way to accomplish this whole thing (consume all the files in a referenced project's output folder)?
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users