I know this isn't the exact forum for this, but I'm really confused and don't know where else to turn. I'm in the process of moving our installer to an msi-based install using WiX. Our application is fairly complex, including .NET assemblies, a client-side application, Windows services that run on a server, a web portal, and COM components on the server that the service and web portal use. It's these COM components that are giving me fits. I've created WiX install elements for the COM components (<Typelib>, <Class>, <ProgId>, <Interface>, etc.), and as far as I can tell the COM registration is correct. All of the COM registry entries are getting created by the installer. However, my COM components cannot be used by their consumers after the installation.
If I use regsvr32 to unregister and reregister the .dll, the COM components work properly. These are VB6 dlls in the main, but I don't think that has anything to do with it. I've watched what regsvr32 does using procmon, and it does look like it's registering my Interface information twice, but I can't see how that would affect things. I'm going to try a full registry comparison next, but I was wondering if anybody here has run into anything like this? --Jim Evans Numara Software, Inc. ------------------------------------------------------------------------- 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
