We've since corrected the issue and moved the COM object to a site-specific DLL whose component only gets installed when the site-specific feature is selected. The problem arises when we try to remove the keys associated with the site-specific COM class from installations that don't require it.
We've placed entries in the RemoveRegistry table in order to remove the keys and all subkeys of the object to no avail. All that gets removed is the default key for the CLSID of the COM class, all the subkeys remain, including the Implemented Categories, and the InprocServer32.
Needless to say that these keys cause problems when the application enumerates the COM classes implementing a category since the registered DLL no longer provides those classes.
My question then is how do I permanently remove these keys from installations in Minor upgrade scenario?
Thanks in advance for any help.
Edited by jerry.ferentinos, 22 December 2005 - 18:28.