I, for one, am glad there is a Start attribute on the ServiceControl
element. We have several services in our product that work in
combination with each other and are needed to be started before the
install finishes as several custom actions run utilities that configure
the system and depend on the services being started. Not my design, but
WiX does the right thing for me. But, one of our other services relies
on a component in the GAC so for that one I use a delayed custom action
to NET START the service.
Here's an example of one service being started after InstallFinalize
<CustomAction Id="NETSTART" Property="NETSTART" Value="NET START
"HFS Hosting Service"" HideTarget="yes" />
<CustomAction Id="caNETSTART" Return="check" ExeCommand="[NETSTART]"
Directory="TARGETDIR" HideTarget="yes" />
And in the InstallExecuteSequence
<Custom Action="NETSTART"
After="InstallFinalize"><![CDATA[&FrameworkRole = 3]]></Custom>
<Custom Action="caNETSTART"
After="NETSTART"><![CDATA[&FrameworkRole = 3]]></Custom>
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adam Majer
Sent: Wednesday, November 14, 2007 11:08 AM
To: WiX Users
Subject: Re: [WiX-users] Services + Vista + GAC
Richard wrote:
> In article <[EMAIL PROTECTED]>,
> Adam Majer <[EMAIL PROTECTED]> writes:
>
>> Regarding the service now, I think the problem has a lot to do with
the
>> installation of stuff into the GAC (the recommended way of doing
things
>> after all). All that the service needs is the C runtime, nothing
special
>> here. But that is not available.
>
> As Phil mentioned, an easy solution to this is to link to the C
> runtime staticly and then *poof*, the problem goes away.
Actually, that is not the 'easy' solution!
There are other dependencies (not assembies, just regular DLLs) and
those would have to reconfigurured and rebuilt.
> ServiceControl does more than *start* services. Plenty of times you
> need to stop services before you upgrade or install things, otherwise
> the service process keeps it loaded in memory and you can't update it
> without rebooting. IIS can hold onto your vdir, for instance. For
> your own services, you need to stop them before you can update them.
> I've used ServiceControl to start services I've installed plenty of
> times, but in this particular case (changes you need aren't done until
> InstallFinalize or later), it isn't working, so I was saying why not
> investigate if you can live without starting the service after you've
> installed it. Its a workaround.
I know this. My question was why have the start attribute of the
ServiceControl tag? Maybe a good feature for future release of WiX may
be a delayed start of services. That is, the service is started after
installation finalizes?
- 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
