Thanks for your confirmation.
Kind Regards,
Sampat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068p7600104.html
Sent from the wix-users mailing l
I just realized that WiX appends a merge module GUID to all IDs during wxs
compilation. So it's not the problem that heat.exe generates non unique IDs
with -suid option, the IDs will become unique when wxs will be compiled to
merge module. So, yes -suid option fully meets my requirements.
--
Vie
I think you can use -SUID parameter to heat.
sampat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-How-to-generate-unique-but-human-readable-IDs-for-directories-components-and-files-tp7600068p7600071.html
Sent from the wix-users mailing
Yeah, I know. For now there is some post-build script that corrects all IDs
every time my merge module built. But this is workaround. The most proper
way is native support of unique human-readable names in heat.exe I think.
--
View this message in context:
http://windows-installer-xml-wix-tools
You can run heat with unique IDs and then apply a XSLT transform to prefix
each ID with the file name.
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX & InstallShield
--
View this message in conte
When heat.exe harvests directory it generates unique but human unreadable
directories, components and files IDs:
There is option -suid, that forces heat.exe to generate human readable but
non unique IDs like *File.txt_2*.
Does heat.exe have an option to generate human readable and u
Any reason you aren't using the HeatDriectory task?
-Original Message-
From: newuser2014 [mailto:wamplersovere...@gmail.com]
Sent: Wednesday, September 24, 2014 10:24 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat.exe harvesting question
Hi,
I hav
Hi,
I have the following pre-build event for wix.
"$(WIX)bin\heat.exe" dir
"$(ProjectDir)/../src/bin/$(ConfigurationName)/MyAppInt" -cg MyAppFiles -gg
-scom -sreg -sfrag -srd -dr AV -var var.MyAppFilesDir -out
"$(ProjectDir)Fragments/MyAppFiles.wxs"
I have my MyApp.exe and MyApp.exe.config files
ese components unless you will be forcing a
major upgrade. Since changing component IDs on a minor upgrade is getting
into dangerous territory.
Regards,
Bevan Weiss
SAGE Automation
>Date: Wed, 19 Mar 2014 10:11:38 +0530
>From: Ravishankar
>Subject: [WiX-users] Heat.exe harvesting c
Hi,
Am facing a strange issue, i have a dll(VB6 created) with name =
LITA300.dll and when i extract using Heat.exe it generates a set of
Component ID and FileID
Now if i change my dll name = lita300.dll , the heat.exe is generating a
different set of Component ID and FileID
"C:\Program Files (x
Tue, 18 Feb 2014 16:43:27 +0100
> >From: Ilir Bekteshi
> >Subject: [WiX-users] Heat.exe Exception with MSBuild and HeatDirectory
> >
> >I have a HeatDirectory in wixproj and it works fine when i build from VS
> but when i try to build with MSbuild it crashes with the er
s
definitely in Windows 8 and above)
Is v3.7.1224.0 the version that you are expecting?
Bevan
-Original Message-
>Date: Tue, 18 Feb 2014 16:43:27 +0100
>From: Ilir Bekteshi
>Subject: [WiX-users] Heat.exe Exception with MSBuild and HeatDirectory
>
>I have a HeatDirectory in
I have a HeatDirectory in wixproj and it works fine when i build from VS
but when i try to build with MSbuild it crashes with the error below. Does
any one have any idea why is this happening?
Unhandled Exception: System.BadImageFormatException: Could not load file or
assembly 'file:///E:\TFS\\to
, Inc.®
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> jocoo...@jackhenry.com
> www.jackhenry.com
>
>
>
> -Original Message-
> From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
> Sent: Monday, December 16, 2013 4:48 AM
> To: Gene
about the WiX toolset.
Subject: [WiX-users] heat.exe : warning HEAT5151
Hi All,
I am creating a WIX installer. In the heat part i am getting the below
warning:
heat.exe : warning HEAT5151 : Could not harvest data from a file that was
expected to be an assembly:
D:\configRelease\command_process
Hi All,
I am creating a WIX installer. In the heat part i am getting the below
warning:
heat.exe : warning HEAT5151 : Could not harvest data from a file that
was expected to be an assembly:
D:\configRelease\command_processors\bpolympic\OraclePull.dll. If this
file is not an assembly you can i
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
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
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
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
You can't do it. I use a separate msbuild step to call Saxon to transform my
XML. XSLT 2 is much nicer anyway.
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 26 February 2013 19:17
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat.exe
Hi,
I have below command working very well. but not sure can we pass parameters
to XSLT Template (FilterFiles.xslt) through command line when we pass xslt
template as a parameter to heat command?
"C:\\heat.exe" dir "C:\Workspaces\Chatra\Website\SCBUDirect.B2CWeb" -cg
SCBUDirect -gg -t "C:\Workspa
Read the heat documentation.
Harvest a directory
heat dir ".\My Files" -gg -sfrag -template:fragment -out directory.wxs
You don't have to install msi to check the effect of Heat params.
See generated "SCBUFragment.wxs" for details.
Anything included in fragment file will be part of your installati
Hi i am using below statement for harvesting the web application.
"%WIX%bin\heat.exe" dir "$(Wixdest)" -cg SCBUDirect -gg -scom -sreg -sfrag
-srd -dr INSTALLLOCATION -var env.Wixdest -out
"C:\Workspaces\Chatra\SCBUFragment.wxs"
And when I install the MSI the resulting folders just contain .dll,.
That, or add the generated wxs file to your project in visual studio.
-Original Message-
From: Yawar Khan [mailto:yawar.k...@live.com]
Sent: 13 February 2013 07:14
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat.exe
SET WIX=""
SET WORKING=""
*To
SET WIX=""
SET WORKING=""
*To harvest*
"%WIX%/bin/heat.exe" dir "%WORKING%\..\exe\plugin" -cg pluginFiles -gg -scom
-sreg -sfrag -srd -dr INSTALLLOCATION -var var.PluginProjectDir -out
..\Fragments\pluginFilesFragment.wxs
[You may use/skip -sreg, -sfrag, -dr, -var according to your need]
*Candle
Thanks pal for reference .
Now I was able to create the .WXS which is output of Heat.exe and it does
contain all the components of the Web directory specified as source
directory.
But now how could I integrate or refer the generated .WXS ;the out put of
Heat.exe in the Installer setup so that whe
Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: 11 February 2013 22:19
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat.exe
Thanks Steve,
Intially cmd was notable to
Thanks Steve,
Intially cmd was notable to recognize Heat.exe as internal or external cmd.
Now was able to fingure out heat.exe from Wixtool bin.
After harvesting the with Heat.exe a fragment file of .WXS is generated
based on the file structure of web application.But I was thinking the MSI
file
Run "heat.exe /?" at a cmd prompt this will list all the parameters
Steve
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: February-11-13 4:33 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat.exe
Hi I am new to WIX,
Can any one
Hi I am new to WIX,
Can any one help me in pointing the heat.exe. Does it comes with WiX tool?
And what are the steps or Command to run the Heat.EXE.
Thanks in advance.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483.html
Sen
Aha, thanks to Bill, Jacob, and Germano for the suggestions. "-scom -sreg"
seems to do the trick.
Regarding the original question, what is -scom useful for? Are there
situations where Class and ProgID elements are not desirable? I'm wondering
if the usage statement for that flag should be clari
Sent: Tuesday, January 08, 2013 2:43 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat.exe, "suppress COM" usage (-scom)
I'm harvesting a directory/file structure. I do not want COM visible
files to be COM registered - this is for a server-side product that
doesn't
x-users@lists.sourceforge.net
Subject: [WiX-users] Heat.exe, "suppress COM" usage (-scom)
I'm harvesting a directory/file structure. I do not want COM visible files to
be COM registered - this is for a server-side product that doesn't use
registry-based COM. Some of the ass
I'm harvesting a directory/file structure. I do not want COM visible files
to be COM registered - this is for a server-side product that doesn't use
registry-based COM. Some of the assemblies are COM visible, so heat
harvests registry information. I tried adding the "suppress COM" (-scom)
option
> >
> > Windows Installer can handle 1200 components easily. ComponentGroups and
> > ComponentGroupRefs can simplify managing large numbers of components in
> the
> > source code.
> >
> >
> > -Original Message-
> > From: Alexey Ivanov [m
.com]
> Sent: 21 June 2012 08:57
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] heat.exe generate component for files in each
> folder, not to generate component for each file.
>
>>so if the first file in a component exists and is of the c
simplify managing large numbers of components in the
source code.
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: 21 June 2012 08:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe generate component for files in each
fo
gt; present. Is there a reason you don't want to utilize a component per file?
>>
>> -Original Message-
>> From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
>> Sent: Thursday, June 21, 2012 12:17 AM
>> To: wix-users@lists.sourceforge.net
>> Subj
e a reason you don't want to utilize a component per file?
>
> -Original Message-
> From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
> Sent: Thursday, June 21, 2012 12:17 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] heat.exe generate component for fil
M
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe generate component for files in each folder, not
to generate component for each file.
like this https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: >heat dir install_files -gg -suid -sfr
like this https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs
is possible with wix?
if i run: >heat dir install_files -gg -suid -sfrag -srd -out 1.wxs
Components for
Hi All,
I've just reinstalled a new laptop with VS2008, Wix3.5 but now when I try
build my projects the setup projects fail to build with the following error:
heat.exe(0,0): error HEAT5307: Build failed.
All the links I see on the internet refer to C++ projects. These however
are C# projects.
al Message-
> From: sangeeta1 [mailto:snmsn...@gmail.com]
> Sent: Friday, December 10, 2010 11:11 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer,
> Name, Title, version
>
>
> The source .wxs file that Heat.exe
t; > email]<http://user/SendEmail.jtp?type=node&node=5824258&i=0>]
>
> > Sent: Friday, December 10, 2010 10:18 AM
> > To: [hidden email]<http://user/SendEmail.jtp?type=node&node=5824258&i=1>
> > Subject: Re: [WiX-users] Heat.exe - How to pass Product
efore printing this e-mail
> -Original Message-
> From: sangeeta1 [mailto:snmsn...@gmail.com]
> Sent: Friday, December 10, 2010 10:18 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer,
> Name, Title, version
>
eeta1 [mailto:[hidden
> email]<http://user/SendEmail.jtp?type=node&node=5824029&i=0>]
>
> Sent: Friday, December 10, 2010 9:38 AM
> To: [hidden email] <http://user/SendEmail.jtp?type=node&node=5824029&i=1>
> Subject: Re: [WiX-users] Heat.exe - How to p
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name,
Title, version
Thanks a lot for these details!
Taking your Manufacturer xsl as a baseline example, I tried to replace the
Name attribute in but really made no progress. I got this crappy
code to work,
.fiserv.com
> Please consider the environment before printing this e-mail
>
> > -Original Message-
> > From: sangeeta1 [mailto:[hidden
> > email]<http://user/SendEmail.jtp?type=node&node=5820142&i=0>]
>
> > Sent: Wednesday, December 08, 2010 8:47 PM
> &
t;
> >
> >
> >
> >
> > Notice that File/@Source="$(var.CodeDir)\code\test.txt" just like the
> > documentation says.
> >
> > In a element is *not* generated in either example.
> >
> > Edwin G. Castro
&g
c Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: sangeeta1 [mailto:[hidden
> > email]<http://user/SendEm
rvices
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: sangeeta1 [mailto:[hidden
> > email]<http://user/SendEmail.jtp?type=node&a
2010 1:58 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Heat.exe - How to pass Product Manufacturer,
> Name, Title, version
>
> Heat does not generate a element.
>
> Heat /? shows the following documentation for -var:
>
>-var
eta1 [mailto:snmsn...@gmail.com]
> Sent: Wednesday, December 08, 2010 12:25 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Heat.exe - How to pass Product Manufacturer, Name,
> Title, version
>
>
> Hi all,
>
>I am trying to generate a wxs source file
Hi all,
I am trying to generate a wxs source file using Heat.exe and wanted to
check if I can pass values for Manufacturer, Name, Title and version to
heat.exe? I tried using -var argument, but does nt seem to update it to the
source file
heat.exe dir c:\temp\Configuration\Files -ag -cg MyCom
[mailto:luca.taro...@faacgroup.com]
Sent: Monday, October 18, 2010 4:55 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] heat.exe runtime error (r6034)
Brian,
Thank you for the detailed explanation. I will definitely consider this
issue.
I know that the company is ISV for Miscro
Brian,
Thank you for the detailed explanation. I will definitely consider this
issue.
I know that the company is ISV for Miscrosoft, however, if there is only one
doubt about rights to create a single package that includes both the
application and SQL server express, my suggestion to them will
Hey Luca,
Distribution and repackaging are two different matters. I highly doubt you
have the rights to repackage SQL Server. If you consume their MSI's and/or
merge modules "as-is" I am sure this would be fine. However, when you change
their deployment packages you have effectively created a diff
yes, it is.
The company where I work is allowed to distribute SQL server.
However, I figured out the issue: the problem wes due to some switches on
heat command.
If I need to include in my .msi file all the installation package I need to
use "-sreg" in order to avoid that heat looks for registry
?
-Original Message-
From: Mark Simonetti [mailto:ma...@opalsoftware.co.uk]
Sent: Tuesday, October 12, 2010 1:57 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe runtime error (r6034)
Still get the same problem here too. Not sure that there
Still get the same problem here too. Not sure that there's a solution
at the minute.
Anyone got any ideas on this?
Thanks,
Mark.
On 12/10/2010 08:20, zero51 wrote:
> Hi,
>
> I got the same problem. I am trying to harves by using heat a whole
> installation of SQL Server 2008.
>
> the error
Hi,
I got the same problem. I am trying to harves by using heat a whole
installation of SQL Server 2008.
the error is the same:
R6034
An application has made an attempt to load the C runtime library
incorrectly.
Please contact the application's support team for more information."
... and af
o: General discussion for Windows Installer XML toolset.
Sent: Wed, October 6, 2010 5:12:51 PM
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
So, the answer is good luck using harvesting tools as they may not
always work. Not really a confidence booster, but they seem to work
fo
ing Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Jon W
To: General discussion for Windows Installer XML toolset.
Sent: Wed, October 6, 2010 5:12:51 PM
Subject: Re: [WiX-users] heat.exe registry harvesting: P
gt; From: Christopher Painter [mailto:chr...@deploymentengineering.com]
> Sent: Wednesday, October 06, 2010 12:14 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
>
> I know you prefaced your opion
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Wednesday, October 06, 2010 12:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
I know you prefaced your opion with "idea
ler XML toolset.
Sent: Wed, October 6, 2010 1:53:41 PM
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
It is recommended that COM dlls be harvested on a machine that approximates
the target machine as close as possible. Realize that due to the nature of
harvesting that there
r 06, 2010 6:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine be 32-bit, etc...? These are
32-bit c++ dlls.
Thanks,
Jon
On Tue, Oct 5, 2010 at 10:10 PM, Blair wrote:
> You don't say if the XP is 32 or 64 bit. You
o: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] heat.exe registry harvesting: ProxyStubClassId
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
When I use heat.exe v3, or tallow.exe to gather registry information
on W
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank
ngine.co.uk]
> Sent: Thursday, September 23, 2010 2:27 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Heat.exe
>
> Thankyou Bob,
>
> This now works fine!
>
> Is it possible to set the variable within the main.wxs file so that
@lists.sourceforge.net
Subject: Re: [WiX-users] Heat.exe
On 22-Sep-10 18:11, David Amey wrote:
> Basically I'm using heat to harvest a folder, simples. However I'm
using the "-var" property in the command line (to replace the
"sourceDir" in the output component'
On 22-Sep-10 18:11, David Amey wrote:
> Basically I'm using heat to harvest a folder, simples. However I'm using the
> "-var" property in the command line (to replace the "sourceDir" in the output
> component's source attribute), using a variable declared in the main.wxs.
> This replaces the "
Hi everyone!
I've been struggling with this problem for a while, if anyone can help I would
really appreciate it.
Basically I'm using heat to harvest a folder, simples. However I'm using the
"-var" property in the command line (to replace the "sourceDir" in the output
component's source attrib
Hi all,
I'm trying to harvest some files (postgres 9.0 for windows to be
specific) using heat.exe. At the moment I'm keeping the command line
very simple:
heat dir pgsql -o test.wxs
While heat is processing, I often get the following pop up:
"Microsoft Visual C++ Runtime Library
Program: C
t 2010 22:46
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] heat.exe does not export COM information for a
.NET component dll
On 10-08-31 3:25 PM, Lian Jiang wrote:
> Hi,
>
> I am using WIX 3.0 to export the COM registry setting from a managed
component dll but I only get a fi
On 10-08-31 3:25 PM, Lian Jiang wrote:
> Hi,
>
> I am using WIX 3.0 to export the COM registry setting from a managed
> component dll but I only get a file without the COM information. I can use
> regasm to registery this dll.
>
> I use the same heat.exe to export another .net component dll succe
Hi,
I am using WIX 3.0 to export the COM registry setting from a managed component
dll but I only get a file without the COM information. I can use regasm to
registery this dll.
I use the same heat.exe to export another .net component dll successfully. The
only difference of these two dlls are
ered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: jeff00seattle [mailto:jeff_tan...@earthlink.net]
Sent: 29 April 2010 07:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] heat.exe: Harvest contents of direc
I took some hunting but I found the flag (have not tried it yet)
http://www.tramontana.co.hu/wix/lesson6.php
http://www.tramontana.co.hu/wix/lesson6.php
Yet another switch, -srd will suppress the identifier generation for the
root folder specified. File components in the root folder will refer
Thanks for the reply,
However, I do not see suppress root directory flag viewing the following
heat.exe documentation link:
http://wix.sourceforge.net/manual-wix3/heat.htm
http://wix.sourceforge.net/manual-wix3/heat.htm
-
Thanks
Jeff in Seattle
--
View this message in context:
http://win
There's a suppress root directory flag on heat.exe that controls this for you.
Thanks,
Navid
-Original Message-
From: jeff00seattle [mailto:jeff_tan...@earthlink.net]
Sent: Wednesday, April 28, 2010 3:14 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] heat.exe: Ha
Hi
I have a directory .\foo\ that has contents I want to harvest.
However, in the end, my INSTALLDIR within Harvester.wxs contains directory
foo and then its components, and I want only want is components.
In other words, my current harvest is this...
But I wan
Oohhh... nifty! Thanks for pointing that out Bob :)
On Sun, Apr 25, 2010 at 11:42 PM, Bob Arnson wrote:
> On 4/22/2010 7:29 PM, Sascha Beaumont wrote:
>> No, heat doesn't harvest 64-bit information.
>>
>> I just do a find/replace (sed would work from the command line if it
>> needs scripting)
>>
On 4/22/2010 7:29 PM, Sascha Beaumont wrote:
> No, heat doesn't harvest 64-bit information.
>
> I just do a find/replace (sed would work from the command line if it
> needs scripting)
>
> Find: Guid="*">
> Replace: Guid="*" Win64="yes">
>
If you use the -arch switch, Candle will do that for yo
No, heat doesn't harvest 64-bit information.
I just do a find/replace (sed would work from the command line if it
needs scripting)
Find: Guid="*">
Replace: Guid="*" Win64="yes">
Sascha
On Fri, Apr 23, 2010 at 9:22 AM, jeff00seattle
wrote:
>
> Hi
>
> I am using heat.exe of WiX 3.0.
>
> Can it
Hi
I am using heat.exe of WiX 3.0.
Can it add attribute Win64="yes" to Component elements when it harvests?
-
Thanks
Jeff in Seattle
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Add-attribute-Win64-yes-to-Component-elements-tp4947
Thanks for the reply
I compared source and MSI extraction using http://winmerge.org/ WinMerge ,
and it showed no difference.
-
Thanks
Jeff in Seattle
--
View this message in context:
http://n2.nabble.com/heat-exe-warning-limit-of-1600-components-per-feature-what-will-happen-tp4928703p4928
Actually, this has been deprecated in Wix 3.5. Windows Installer no longer
has this restriction.
To your questions, WiX would have been fine. The issue would have been on
machines before Windows 2000.
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove
On
heat.exe : warning HEAT5155 : Although there are no limitations to the size
of a ComponentGroup, Windows Installer has a limit of 1600 components per
feature. Please consider reducing the size of ComponentGroup
'$(var.ComponentGroupName)' from current count of '3037'.
What is the impact of my ins
On 3/3/2010 5:02 AM, Jacek Pospychała wrote:
> anyway, I'm still interested to learn, how the DLL is processed that it can
> throw a popup..
>
Self-reg runs code in the DLL; it can do anything, which is one of the
reasons it's evil in an installer.
--
sig://boB
http://joyofsetup.com/
ok, I figured out adding "-sreg" to heat command line does the trick.
anyway, I'm still interested to learn, how the DLL is processed that it can
throw a popup..
Jacek
2010/3/3 Jacek Pospychała
> hi,
>
> I'm generating wxs file for Sun Java Runtime using heat and unfortunately
> during this p
hi,
I'm generating wxs file for Sun Java Runtime using heat and unfortunately
during this process, heat/jre popups an error dialog saying "Java Plug-in
1.6.0_18 is not installed properly".
This happens for two DLL files inside JRE and turns our sleek fully
automated process into manual nightmare :
Yeah, it's not trivial but we should solve this problem eventually.
On Thu, Jan 14, 2010 at 8:52 AM, Brian Rogers wrote:
> Not sure if it is that straight forward. I think the reason we keep punting
> this feature is the dependencies heat.exe has on the Wix core project (
>
> http://sourceforge.n
Not sure if it is that straight forward. I think the reason we keep punting
this feature is the dependencies heat.exe has on the Wix core project (
http://sourceforge.net/tracker/index.php?func=detail&aid=2012626&group_id=105970&atid=642717
).
Brian Rogers
"Intelligence removes complexity." - Me
h
On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote:
> Is there a particular reason why Heat.exe is targeted and compiled
> specifically against the x86 architecture?
Because an MSIL .exe runs as a 64-bit process on an x64 system, so it
couldn't load x86 DLLs. I suspect there's a need for Heat64.
Is there a particular reason why Heat.exe is targeted and compiled specifically
against the x86 architecture? I have seen a couple of questions about this
around on the Internet but no firm answer or resolution. I briefly looked over
the Heat code (v3.0.5419.0) and there does not seem to be anyt
I see two directories listed below. You should only have one.
"C:\Program Files\Windows Installer XML v3\bin\heat.exe" dir
"..\..\~tmp\j2build3v_win\apps" -gg -sfrag -scom -sreg
"$(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu" -out
"$(ProjectDir)gen_fragment.wxs" -template:fragment
Should be:
Hi,
I have some problems to migrate from WIX 3.0.4707 to WIX 3.0.5419 because the
arguments of HEAT.EXE changed.
usage: heat.exe harvestType harvestSource -o[ut]
sourceFile.wxs
What is meant with the new argument harvestSource?
The old command looks like this:
"C:\Program Files\Windows Installe
1 - 100 of 124 matches
Mail list logo
