> > Another solution that was suggested here was to use a deferred custom > action to start the service. But that also doesn't seem to work. Using > WiX 2.x branch and it results in a runtime error. The custom action > works OK if run outside of the MSI. The error returned is > > "Unable to schedule operation. The action must be scheduled between > InstallInitialize and InstallFinalize." > > Currently I have it as, > > <Binary Id="blah" SourceFile="...."/> > > <CustomAction Id="blah_ca" ExeCommand="" BinaryKey="blah" > Execute="deferred" Impersonate="no" Return="ignore" /> > > <InstallExecuteSequence> > <Custom Action="blah_ca" OnExit="success" /> > </InstallExecuteSequence> > > Any ideas?
I could be wrong but, I think your problem is that you're trying to use a binary that's embedded in the msi and this is only available between InstallInitialize and InstallFinalize. After InstallFinalize, all the temporary bits of your msi have been cleaned up. To run a custom action as late as you need, it has to be something you install or something already on the system. ------------------------------------------------------------------------- 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
