Bob Arnson-6 wrote: > > Karim MacDonald wrote: >>> would replace the <Class> element, or if this particular Heat bug (think >>> I >>> saw it logged but can't find it now!) is likely to be fixed any time >>> soon? > > So far, nobody's volunteered to maintain Heat so the bug isn't likely to > fixed soon. > I may see if I can fix this particular bug on my own system. I don't know how patch submissions work, but naively expect that I might then be able to submit a patch for inclusion at some date?
Bob Arnson-6 wrote: > > Both are bad because they violate component rules. > Could you be more specific about which rules they break please Bob? I've checked MSDN and although the same registry value is being written to twice, I can't see a component rule problem as long as this all happens within one component. Bob Arnson-6 wrote: > > Is it not enough to remove the mscoree.dll InprocServer32 value? > Unfortunately the mscoree.dll value is correct & not the problem: it's needed so that COM knows to prod .NET when the object is CoCreated. The root problem (I think) is that Heat is wrongly guessing the content of that registry value when it doesn't need to. A clean work-around would be a short dark.exe segue and then ditch the <Class> element from the authored code (I might do this). -- View this message in context: http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13250119 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
