'Content' and 'Satellites' project types do not do anything

[wixbot]

1. Create a project to harvest with Heat
2. Harvest the project with this command line:

   heat.exe project -pog:Content test.csproj -out product.wxs
   OR
   heat.exe project -pog:Satellites test.csproj -out product.wxs

Expected: Either a wxs file is created by heat or if the project output group is not applicable, a warning is displayed

Actual: There is not output generated by heat.exe. It appears to just run and do nothing.

Originally opened by candyc from http://sourceforge.net/p/wix/bugs/1801/

[wixbot]

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

[wixbot]

I'm having a similar issue after upgrading from 3.5 to 3.10.

The command following command produces an empty ComponentGroup. (and no error)

Heat.exe project <path_to_project_no_spaces>\A_Project.vcxproj -configuration Debug -platform Win32 -pog Content -projectname A_Project -v

<?xml version="1.0" encoding="utf-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
    <Fragment>
        <ComponentGroup Id="A_Project.Content" />
    </Fragment>
</Wix>

Running with 3.5 it worked, there are files that have "Content" set to true, and "Item Type" is "Content"

Originally posted by serge
Status changed from Closed to Untriaged

[wixbot]

Looks like the problem lies with heat and VS2015.

We are upgrading a project from VS2010 to VS2015, along with it WiX from 3.5 to 3.10

The problem lies in a vcxproj that is now a VS2015 project file, Running heat (v3.10) on a VS2010 project file before upgrading to VS2015 heat works as expected.

The command line output from running against VS2015
Windows Installer XML Toolset Toolset Harvester version 3.10.1.2213
Copyright (c) Outercurve Foundation. All rights reserved.

Found ToolsVersion 14.0 inside project file.
Loading project using MSBuild version 14.0.

The Command line output from running against VS2010
Windows Installer XML Toolset Toolset Harvester version 3.10.1.2213
Copyright (c) Outercurve Foundation. All rights reserved.

Found ToolsVersion 4.0 inside project file.
Loading project using MSBuild version 4.0.

Originally posted by serge

[wixbot]

Release changed from v3.5 to v3.x

[redoranges]

I have been having this problem for over a year, my workaround was to hard code content in a wxs file, but that is error prone when some adds a content file to the project but does not add a corresponding line in the wxs file.

Is there any chance this issue will be looked at or a better workaround recommended?