Heat cannot handle COM server EXEs. You'll have to write the appropriate
registry entries yourself. See the <Class>, <Interface>, <ProgId>, <TypeLib>
elements. You should strongly consider using non-advertised entries - see
Rob's blog entry at
http://robmensching.com/blog/archive/2007/03/12/RobMens-Recommendation-Do-no
t-advertise-COM-information-in-MSI.aspx.
If it's a C++ EXE, you should be able to work out what's needed from the
code. If it's a VB6 'ActiveX EXE' you'll need to find out the GUIDs it's
using, for which you can use OleView from the SDK.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Bardon
Sent: 15 March 2007 21:17
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] problem with exe COM server and heat
I'm working with an installer that registers an exe COM server, but the
catch is that the main application is .net. This means that I have a COM
exe, a Proxy stub DLL, and an interop DLL to contend with. I ran heat on
all three elements, and put the registry settings in the wix source. After
I install though, the .net application can't create the COM component. When
I manually run the exe with the /regserver flag after installing though,
everything works. Is there something else I need to know about extracting
registry data using heat besides just running "heat.exe file filename -out
source.wxs" on the exe, proxy stub, and interop DLLs?
Thanks again for all the help-I think I might be starting to get a handle on
at least bits of the framework :)
Chris
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
