http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Wix-3-5-Heat-Cannot-harvest-64-Bit-COM-DLL-Registry-Data-td7583833.html
http://sourceforge.net/p/wix/feature-requests/399/
The first is a reference to someone having a possible solution, the second is a
link to the feature request
There are number of ways of achieving results results.
1) As told by Gabriel
2) Don't include -srd switch to harvest root directory as element.
3) use -var in Heat and -d in candle.
e.g for 3
heat.exe dir "$(SolutionDir)MyProject\MyDirectory" -ag -sfrag -srd -var
"var.MyProjectDir" -out $(ProjectD
Hi,
And with this :
*heat.exe dir "$(SolutionDir)MyProject" -ag -sfrag -srd -var
"var.MyProject.ProjectDir" -out $(ProjectDir)HarvestedFiles.wxs"*
Or you could add a subdir "Sources" in your SolutionDir :
C:\\SolutionDir\MyProject\Sources\MyDirectory
*heat.exe dir "$(SolutionDir)MyProject
No this is the right group. Might just take more than one day to get to your
question though.
On Fri, Mar 11, 2011 at 7:10 AM, Hoover, Jacob
wrote:
>
> Am I asking this question in the wrong group? After downloading the
> Wix source and pondering on this a bit further, instead of taking a list
>
Am I asking this question in the wrong group? After downloading the
Wix source and pondering on this a bit further, instead of taking a list
of dependent dlls I believe it would be better to take a single/list of
fragments containing the harvested data of the dependent component.
Jacob
-Or
And that was after we found 5+ other bugs with no end in sight. VS doesn't
make this easy because all the different project systems are unique and when
you do things wrong something blows up mysteriously.
We really want this feature but it's going to take more effort to get
working than we have ti
When I looked at the code I found it was not easy to do. There is an
open bug for it:
http://sourceforge.net/tracker/index.php?func=detail&aid=2998492&group_i
d=105970&atid=642714.
Neil
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: 19 November 2010 1
e-
> From: Tency Kuruvilla [mailto:tency.kuruvi...@kcs.com.kw]
> Sent: 31 March 2010 12:04
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Heat harvesting and fragment/component generation.
>
> try
>
> heat.exe -out sourceFile.wx
]
Sent: 31 March 2010 12:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat harvesting and fragment/component generation.
try
heat.exe -out sourceFile.wxs Supported
harvesting types:
dir harvest a directory
file harvest a file
project
try
heat.exe -out sourceFile.wxs
Supported harvesting types:
dir harvest a directory
file harvest a file
project harvest outputs of a VS project
website harvest an IIS web site
Options:
-ag autogenerate component guids at compile time
-gg generate guids
As an example, here is the heat output for a couple of the files in one of the
folders:
Budnik, Christof (SCR US EXT) wrote:
+ I am also wondering if there isn't an option to prevent "heat" from
generating such tags and deals with .dlls in the same way it does with
other files.
Not currently.
If not, how should the generated file be used without editing it?
In general, heat i
12 matches
Mail list logo
