Evans, Jim wrote: > 1. What is the best way to harvest the registry entries for each COM > component? I could use heat, but these are VB6 components, so I get a > bunch of extra stuff in the generated file. I could use tallow from WiX > v2, but I'm not sure that would be any better. I suppose I could export > the registry, register the component, export the registry again, and use > a file comparison tool to generate a list of changes, but that's going > to be tedious and error-prone. >
"Tedious and error-prone" describes the self-registration process. Your best bet is to start with more data, like from Heat, and narrow it down. > 2. What is the preferred way in WiX to author the registration of the > components? I've found conflicting advice on whether to use the <Class> > or <Interface> elements, or just to write raw registry keys directly. > The Class, Interface, etc. elements turn into registry entries unless you mark them Advertise="yes". That avoids the problems with the corresponding MSI tables. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
