Like which ones? -----Original Message----- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 20, 2009 09:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installing a service wich is also a COM server
Yes that is probably what I would do, although you still need <RegistryValue> entries as a few settings are not covered. Neil -----Original Message----- From: Rob Mensching [mailto:rob.mensch...@microsoft.com] Sent: 20 January 2009 15:48 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installing a service wich is also a COM server Why not use the specific Class, ProgId, TypeLib and Interface elements? That's a much easier way to represent all the same registry keys. -----Original Message----- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 20, 2009 06:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installing a service wich is also a COM server I would install the service using the <Service> elements and then do the COM bit by writing the relevant registry entries using <RegistryValue>. The hard bit is generating the registry values as I don't think heat can harvest COM servers, if the code is written in C++ you should be able to get the values from the source registration code. Neil -----Original Message----- From: Michael Baker [mailto:m...@objectivedynamics.co.uk] Sent: 20 January 2009 11:48 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing a service wich is also a COM server I need to produce an msi-style installer for a legacy project and I need to do it fairly quickly. WiX has been recommended to me and so far, so good but one thing eludes me at the moment. One of the targets is both a Win32 Service *and* a COM server. Does anyone have any details on how to handle this kind of scenario? TIA, MikeB ------------------------------------------------------------------------ ------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
