Hi all - I'm working on an install with a somewhat large number of older COM objects and .NET classes exposed to COM. For the most part, heat.exe works very well to move away from self-registration; very impressive.
We have had some issues, like how to deal with the inability of heat to harvest EXE servers. For those I used RegSpy2 (the one on installsite.org) to create .reg files, which can then be used to create .wxs files. The other issue is how to deal with the infamous HEAT5150 warning. Admittedly we have only a few legacy DLL's which are affected. Regspy2 harvests registry entries for these just fine, and I was curious to know why.. After looking through the regspy2 code, and then the Wix UtilExtension code, I realized that they were doing basically the same things -- registry redirection using RegOverridePredefKey. The difference was that regspy2 was initializing the redirected registry with entries for the ATL Registrar COM object (see CreateAtlRegistrar in the regspy2 source code), which enabled these ancient DLL's to self-register. I might modify my copy of UtilExtension, and perhaps add some hack like an -atl switch to enable a similar feature in heat.exe (if I make any progress on getting the source to build :), but primarily wanted to share this observation. Cheers ! -Rob ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
