WinSW is an executable binary, which can be used to wrap and manage a custom process as a Windows service. Once you download the installation package, you can rename WinSW.exe to any name, e.g. MyService.exe.
See the project manifest.
Starting from WinSW v2, the releases are being hosted on GitHub and NuGet.
Due to historical reasons, the project also uses the Jenkins Maven repository as a secondary source. Binaries are available here.
WinSW is being managed by configuration files: Main XML configuration file and EXE configuration file.
Your renamed WinSW.exe binary also accepts the following commands:
install
to install the service to Windows Service Controller. This command requires some preliminary steps described in the Installation guide.uninstall
to uninstall the service. The opposite operation of above.start
to start the service. The service must have already been installed.stop
to stop the service.restart
to restart the service. If the service is not currently running, this command acts likestart
.status
to check the current status of the service.- This command prints one line to the console.
NonExistent
indicates the service is not currently installedStarted
to indicate the service is currently runningStopped
to indicate that the service is installed but not currently running.
- This command prints one line to the console.
WinSW v2 offers two executables, which declare .NET Frameworks 2.0 and 4.0 as targets. More executables can be added on-demand. Please create an issue if you need such executables.
User documentation:
- Installation guide - Describes the installation process for different systems and .NET versions
- Configuration:
- Use-cases:
- Configuration Management:
Developer documentation:
This is a new baseline of WinSW with several major changes:
- Major documentation rework and update
- New executable package targeting the .NET Framework 4.0. .NET Framework 2.0 is still supported.
- Extension engine, which allows extending the wrapper's behavior. And a couple of extensions for it (Shared Directory Mapper, Runaway Process Killer)
- New release hosting: GitHub and NuGet
- Migration of the logging subsystem to Apache log4net
- Bugfixes
The version v2 is fully compatible with the v1 configuration file format, hence the upgrade procedure just requires replacement of the executable file.
WinSW is licensed under the MIT license.