Hi wix-users, I've been looking into migrating as set of Visual Studio MSIs and MSMs to WiX (v2). On the whole things are are going swimmingly!
One issue I haven't quite worked out is about migrating shared merge modules to wix. I've been using the same component guids as the previous VS2005 used (i.e. so that the componentIds match), but the shared COM components are now registered differently (using the recommended TypeLib, Class and ProgId WiX elements, as opposed to the (advertised?) way that VS registers COM). These all install correctly, and co-exist with legacy VS installers at the file level. But there is an issue with the COM registration. The issue is as follows: 1. Install a WiX MSI (containing a WiX MSM, which contains a shared COM component going to common files), *Result:* Works, shared com registered 2. Then install an older VS MSI (containing a VS MSM, which containing the same shared COM file), *Result:* Both apps work, shared com registered 3. Then uninstall the VS MSI. *Result:* WiX install is BROKEN, shared com is unregistered. My guess is that this is to do with the resources (i.e. registry keys) changing for the same component. Does anyone have any suggestions about this issue. With thanks, David ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
