Re: [WiX-devs] Heat over 64 bit dll

[John C. <JoC...@ja...>]

Apologies.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoC...@ja...<mailto:JoC...@ja...>



From: John Cooper
Sent: Thursday, December 18, 2014 10:44 AM
To: sampat magi
Cc: WiX toolset developer mailing list (wix...@li...)
Subject: Re: [WiX-devs] Heat over 64 bit dll

I used to do something like that when I worked at Microsoft.  You need to be careful that ID’s can only be 72 chars.  It never fails that I have file names longer than 72 chars.  Also, it is rather common to have multiple files of the same name deployed, and this requires a system of “incrementing” the ID’s to prevent collision.  There are features that Wix 4.0 may have that will make this much easier (Id scoping is one), but Wix 4.0 is very far from being ready for production.

I have seen no evidence that heat can currently handle 64-bit COM very well.  Of course, the development of heat is entirely up to its fan base.  With all the many ways people want to use and extend it, code would be very welcome to extend heat.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoC...@ja...<mailto:JoC...@ja...>



From: sampat magi [mailto:ssm...@gm...]
Sent: Thursday, December 18, 2014 10:38 AM
To: John Cooper
Subject: Re: Heat over 64 bit dll

Thanks for your reply. :) We are using 64 com dlls.

The mechanically generated ID's are very unpleasant to use when patching becomes necessary, and some of the options usually selected for heat (such as placing all the components in a single fragment) will generate poor patching performance.

1. Yes i do agree with your points. i used -suid to get the ID as name of the file .
2. I was working on install-shield where in each component is different is very easy to maintain component individually. Now we are planning to migrate to WiX. Wix places all components into a single wxs which leads very uncomfortable to read and maintenance. Why dont they incorporate an option which allows to create wxs file for each component?

I suspect it is not 64-bit aware.::

By this line, i understand that heat is not for harvesting 64 bit files? Please correct me if i am wrong here.



Regards,
Sampat

On Thu, Dec 18, 2014 at 9:51 PM, John Cooper <JoC...@ja...<mailto:JoC...@ja...>> wrote:
Well, the general problem is that COM registry entries are going to be in the 32-bit hive (traditionally, COM has been 32-bit).  A heat running as a 64-bit process should be able to see these entries (the converse would not be true).  However, heat hasn't changed much since Wix 3.5, and I suspect it is not 64-bit aware.

Although heat is useful for prototyping and for  extracting certain kinds of information for incorporating into an installer, I do not like using it in production.  The mechanically generated ID's are very unpleasant to use when patching becomes necessary, and some of the options usually selected for heat (such as placing all the components in a single fragment) will generate poor patching performance.

In the one case where I am forced to use heat by project management, the effect is a bunch of files whose key paths change where every build (they wanted the folder number to reflect the file version).  This has consequences.  I have also had build race issues.

This being said, it is undeniably a popular tool.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoC...@ja...<mailto:JoC...@ja...>


-----Original Message-----
From: ssm...@gm...<mailto:ssm...@gm...> [mailto:ssm...@gm...<mailto:ssm...@gm...>]
Sent: Thursday, December 18, 2014 10:08 AM
To: John Cooper
Subject: Heat over 64 bit dll

Hi Sir,

Can heat harvest a dll file which is a 64 bit ? I am using wix 3.9.1006.0 . When i build dll in VS2013 with 32 bit and  i run heat.exe it successfully harvest and give proper wxs file.

Now, if i build the same dll file with 64 bit and run heat over it , heat wount generate the similar kind of wxs. Just a component and a file . No any information about RegistryWrite, TypeLibs etc.

We have all 64 bit dlls in our product , So could you please share your thoughts on the same?

Regards,
Sampat

_____________________________________
Sent from http://windows-installer-xml-wix-toolset.687559.n2.nabble.com

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.