Hi,
We want to ensure that a Windows Service is started correctly after a
successful installation by rebooting the machine since we've had occasional
problems starting it directly from the msi. After the reboot the installation
resumes with starting the installation procedures - such as stopping services,
copying files etc. - all over again and the service is not started. Since we
don't trigger service start from WiX/msi there is no wonder it is not started,
but we definitely don't want the installation to start from the beginning again
after reboot.
The application consists of a Windows Service, a Windows Forms Application, a
Windows Sidebar Gadget, and finally an ActiveX component to make it possible
for Gadget to communicate with the Windows Service using WCF, as the Forms app
and Windows Service also use WCF. All parts are installed by an msi package,
which is compiled and linked with WiX.
The ActiveX component needs registration in Windows Registry to be Com-visible,
but when we omit all registry keys and hence, also ActiveX component and
Gadget, the installation goes fine: The user is prompted for reboot, and when
installation resumes the wizard just shows the finish screen exactly as we
intend to make it to do.
For the reboot we use <ScheduleReboot Before="InstallFinalize">NOT
AFTERREBOOT</ScheduleReboot> in the InstallExecuteSequence.
Is anyone familiar with this?
/Jon
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users