Not today. Heat can't harvest selfregistration code out of executables. Some people posted using a series of tools to do this sort of thing in the archive. Or, you can just enter the Class, AppId, etc elements yourself. I do the latter usually.
On Wed, Dec 5, 2012 at 10:48 AM, Dave Gilmour (FET) <d...@fetcorp.com>wrote: > I have an application (.exe) that has a built-in automation interface. > I tried using heat to generate wxs code for the application, expecting > it to generate code to register the automation interface. > Unfortunately, it only generated code for the .exe file itself. > > Is there a way to make heat generate the appropriate code to register an > automation interface from a .exe, or what is the proper way of going > about this? > > Thanks. > > Dave > > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
