Seems eminently possible using ServiceInstall if you use one Component with one File as the KeyPath & multiple ServiceInstall elements. However if your Services need to be in separate Components then I think you'll need to use Custom Actions.
Unfortunately Windows Installer is the weak link here rather than WiX (as usual). The ServiceInstall table (http://msdn.microsoft.com/en-us/library/aa371637.aspx) has a Component column which requires an "External key to column one of the Component Table. Note that to install this service using the InstallService table, the KeyPath for this component must be the executable file for the service." hence WiX has to follow the same convention otherwise it just won't work. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Stefan Kuhr [mailto:kustt...@gmx.li] Sent: 27 June 2011 13:32 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using the same .exe file for different services in oneMSI? Hello everyone, our product contains multiple services and all use the same .exe file and differ only via their name and command line, where a DLL name is passed that contains the real service code. So the exe file is more or less a reusable framework much like svchost.exe and distinct service functionality is implemented in DLLs. Is it possible to use the WiX ServiceInstall element to install multiple such services from one WiX script or is this simply impossible and I have to resort to a custom action? As far as I see, the File element whose Keypath is set to 'Yes' within the component where the ServiceInstall element resides, is considered the BinaryPath of the service. In my case however, this file element would be the same for different services/components and even worse, other installs that we are about to write in the future will use the same exe file as well so ideally it would be in one component that we reuse across installs. Any help appreciated, -- Stefan Kuhr -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-the- same-exe-file-for-different-services-in-one-MSI-tp6520212p6520212.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
