[wix-users] VS2019 C++ project harvesting

[John Buuck]

For me, the easiest work-around was to change my "heat project" statements to "heat file" statements against the target file of the project.
________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Rob Mensching via wix-users <wix-users at lists.wixtoolset.org>
Sent: Wednesday, October 21, 2020 1:17 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Rob Mensching <rob at firegiant.com>
Subject: Re: [wix-users] VS2019 C++ project harvesting

FireGiant offers a commercial solution for harvesting that works differently and does support this scenario and several others. It is not free but works well.


The FireGiant advanced harvesting is documented here: https://www.firegiant.com/wix/wep-documentation/harvesting/

There is a trial available via links here: https://www.firegiant.com/products/wix-expansion-pack/

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-users
Sent: Wednesday, October 21, 2020 9:45 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Sean Hall <r.sean.hall at gmail.com>
Subject: Re: [wix-users] VS2019 C++ project harvesting

No one has implemented project harvesting in Heat for MSBuild 15+ ( https://github.com/wixtoolset/issues/issues/5490).

On Wed, Oct 21, 2020 at 3:45 AM DUCKA Michal via wix-users < wix-users at lists.wixtoolset.org> wrote:

> Hi All, my first post here, hope not to break any unspoken newbie
> rules 😊
>
> I’m having a hard time updating VS2010 WiX setup project to VS2019 tools.
> What we want to do in same exercise is to migrate C++ projects to v142
> toolset. I’ve tries many ways but still cannot force heat to harvest
> such a project properly. Problem already fought against:
>
>   *   On VS2010 + VS2019 machine – no way to persuade heat to use MSBuild
> + it’s settings from Program files x86\Visual studio\... folder. It
> + was
> always trying to take it from Program files x86\MSBuild
>   *   I moved to new machine with VS2019 only – problem persisted but was
> able to overcome it by setting VCTargetsPath environmental variable.
>   *   Changed ToolsVersion for both C++ project and WiX setup project to
> 15.0 or Current and result is same - cannot go any further because of
> this
> message: heat.exe(0,0): error HEAT5305: Failed to load project
> RibbonBar2017.vcxproj: The expression
> "[Microsoft.Build.Utilities.ToolLocationHelper]::FindRootFolderWhereAl
> lFilesExist(C:\Program
> Files (x86)\Microsoft Visual
> Studio\2019\Professional\MSBuild\Microsoft\VC\v160\;,
> Platforms\Win32\PlatformToolsets\v142\Toolset.props;Platforms\Win32\PlatformToolsets\v142\Toolset.targets;Platforms\Win32\Platform.props;Platforms\Win32\Platform.targets)"
> cannot be evaluated. Method
> 'Microsoft.Build.Utilities.ToolLocationHelper.FindRootFolderWhereAllFilesExist'
> not found.
>
> After reading this I checked around and found out some suggestions
> that it may be related to MSBuild 15 dlls to be registered in GAC and
> that unregistration should help, but it was not the case. I have
> MSBuild stuff in GAC but it v4.0 dlls.
>
> So, my question is simple: is there a way to harvest VC++ v142 project
> using heat.exe on VS2019 only machine? If so, what I missed or did
> wrong to achieve it?
>
> Michał
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/