Script2Service - Run your scripts (javascript / vbscript) as service

Get Started with Script2Service

Steps to Develop a Service

Prepare the Main Script File. It should contains:
- Codes for service initialzation;
- Codes that need to be run from service start to service stop;
Sample
Prepare the Script Files that Export Functions. If you want to export functions for other application to call, these functions should be implemented in separate script files. To ensure the performance of your service, you should avoid putting inrelavent functions and objects into a same script file.
Sample
Build your Service with /um enabled and the 'Start on demand' option checked;
Run you service in /um mode and fix any errors in your scripts.
Repeat 3 ~ 4 untill your service works fine.
Run your service as a real service. It may take days or even weeks of continuous test running before to prove your service's reliability.

Undersantd a Script2Service Project

Key words below in brown are to be found on the Script2Service Screenshot

Key Words	Descriptions
Service Name	Your service's real name. This name does not appears on the Control Panel. When your service is installed, Windows lists this name under "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services". You must carefully choose a name for your service, not to overwrite a existing service.
Display Name	This the name appears on the Control Panel as 'Name'. When your service is installed, this name is also registered as the event source for the Application Log (under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Eventlog\Application).
Dependencies	Names of the services your services depends upon. Default is tcpip/rpcss.
AppID, CLASS ID	These two IDs represent your service in the system registry table. Windows uses them to record configurations. Each service must have their unique AppID and CLASS ID and they must remain unchanged through out the life of the service project.
Description	More detailed information about your service. This also appears on the Control Panel.
Main Script File	A JavaScript file or a VBScript file. This file is loaded automatically when the service is started. There are no special rules for codes inside this file. Typically you do initialzation here, license checking for example. You codes can be some loose lines, a infinite loop waiting for the service to stop, or even nothing at all. The service continues to work after your codes quit, except your codes call Context.StopService();.
Service File	The program file name of your service. Since service program files are usually stored in the system folder, you should choose the name carefully not to overwrite an existing file there. The file name will also be listed under "HKEY_CLASSES_ROOT\AppID" as a sub-key. You must choose a unique file name for your service.
Allow User-mode execution	Whether the service program support the /um switch.
Service stop pending max	How long the service should wait for your script threads to exit.

Service Command Line Arguments

The converted service program accepsts the following command arguments:

/install	Install the service on the current computer. The service is configured as auto-start using the SYSTEM account.
/start	Start the service.
/stop	Stop the service.
/remove	uninstall the service.
/um	Run the service as an interactive programm using the current user's account. To use this option, the service must have been built with Allow User-mode execution checked, installed by not started. In this interactive mode, the LogEvent will write information to the console window, instead of the Application Log. Press ESC will stop the program.

The Life Cycle of a Service Instance

COM/DCOM/Security initialization
Register the Service object so that other applications can connect to it.
Start a thread and load your main scripts.
Wait for SERVICE_CONTROL_STOP command from the System.
Wait a period (specified by your project) for your scripts threads to exit.
Clean up and exit.