Hi Arun, I've been experiencing the same kind of problems and I posted a question about it recently. See the http://n2.nabble.com/Heat-problem-harvesting-class-from-type-library-td1303554.html
I believe the problem is that for executables (.exe out-of-process COM Servers) the WiX heat tool can only harvest the basic type library-information (linked into it), but it cannot harvest the registration information for the CLSID and ProgID's because that registration typically is hard-coded into the executable (and which normally is executed when it is registreded with a "file.exe /regserver" call). I believe that heat.exe is only harvesting the registry information after a call similar to "regsvr32 file.dll" (i.e. the call to DllRegister expected to be found in the in-process COM server's in dlls). Can someone confirm this? If heat.exe also would call what corresponds to "file.exe /regserver" then it would probably also work for .exe out-of-process COM Servers. However as far as I know .exe's can choose to register differently (not supporting the /regserver), in which case heat would not be able to harvest the information. What I ended up doing was to manually add the missing information into my WiX source file (.wxs). Hope this info helps, /Michael information See ------------------------------------------------------------------------- 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
