Well, the latter approach will run the internal custom actions on the
assemblies.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
From: samp
0
|jocoo...@jackhenry.com
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Thursday, December 18, 2014 10:58 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Heat over 64 bit dll
The COM data (classids etc) is typically the same
The COM data (classids etc) is typically the same for both
architectures, so massaging the 32-bit output a little should be all
that's required.
---
Phil Wilson
On Thu, Dec 18, 2014 at 8:21 AM, John Cooper wrote:
> Well, the general problem is that COM registry entries are going to b
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 suspec
4 matches
Mail list logo
