Chris Lord wrote: > I tried adding advertise="yes" but to the Heat output but when I build > it, Candle then complains something about class/@server cannot be > specified at the same time as advertise=yes. This confused me no end as > a couldnt see any reference to the server property. >
It defaults to the File it's a child of. The Class (et al) tables in MSI can't be associated directly with a file; instead, they associate with a component's keypath. So you'll have to do more editing, to move the Class element under the Component element; make sure the File element representing the COM server has KeyPath="yes". (And it's no wonder COM's such a pain...) > I know Heat is problematic from a discussion not so long back in which > Rob asked for volunteers to take over maintenance of the "Heat" code. > Is the is missing registration that's needed likely to be one of those > problems and if so should I give up now trying to get it to work? > AFAIK, for basic COM registration, the biggest problem is that Heat can gather too much or too little data. Heat is trying to reverse engineer the right setup authoring from registry writes. If you have an existing setup that works, you might try using Dark to decompile it instead of using Heat. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
