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 <jocoo...@jackhenry.com> 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 > |jocoo...@jackhenry.com > > > -----Original Message----- > From: ssmcs...@gmail.com [mailto:ssmcs...@gmail.com] > 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. > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
