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.
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? Chris -----Original Message----- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Monday, December 22, 2008 16:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Incorporating Heat output into a project Chris Lord wrote: > One thing I did do was to compare the MSI files of a working > installation created by Installshield for a previous version and the > Wix generated one using Orca. Straight away, I noticed the working > install has a class table and relatively few registry entries but the > Wix has no class table and a large amount of registry entries. I > don't know if this is relevant or not. > WiX prefers to register COM objects using the registry, because the "native" COM tables in MSI lead to weird user experiences when MSI wants to repair. The effect should be the same, however. For comparing the two, you can tell WiX to use the COM tables by specifying Advertised='yes' in each element. Likely Heat is missing registration that's needed. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------ ------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
