We have one service in the installer that replies on a file being installed to the GAC, so the service can't be started until after InstallFinalize. I use a deferred Custom Action to NET START <servicename> and it seems to be working fine for our customers. Just thought I'd mention that option.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Majer Sent: Wednesday, October 24, 2007 9:48 AM To: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Installation order for Service Installs Bob Arnson wrote: > Adam Majer wrote: >> How can I structure this such that the merge module is installed >> completely prior to installing the component? >> > > That's not how Windows Installer works: Merge modules lose their > identity when merged, so they're just a bunch of components in the .msi. > Then, each resource of each component is installed, via standard > actions. (InstallFiles, for example, installs all the files in all > components before WriteRegistryValues writes all the registry values for > all components.) > > If you need tighter control than that, you need to use separate packages > and a chainer. > Are you saying that it is impossible to install a service that depends on a MSVC runtime and start it in the same installer? Surely, that can't be true. The installation keeps bombing that SxS install is not correct. Now, if I do not attempt to start the service, installation completes and I can start the service manually, through reboot or use a program that uses the same runtime SxS. It is as though SxS is not installed until after the installer is done making it unavailable to anything (including custom actions) called by the installer. The structure of the installer is very simple. <directory...> <directory ...> <component id="service"> <File id="service".....> <ServiceInstall ....> <ServiceControl start="install" ...> </component> </directory> <merge id="vcrt80" .../> </directory> <feature id="service" level="1" ..> <componentref id="service"> <mergeref id="vcrt80"> </feature> Therefore, to start services that need the SxS module installed by the same MSI, * reboot like in old days to start, * start manually, or * ??????? - Adam ------------------------------------------------------------------------ - 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 ------------------------------------------------------------------------- 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
