A wrapper executable that can run any executable as a Windows service, in a permissive license.
Windows 服务封装器.

NextTurn ea6cb8062a Remove strong name signing před 6 roky
.github bdbc6a0812 Update tag format před 5 roky
doc 9b8d8083f0 Remove offline mode section from installation guide před 5 roky
eng 749612b978 Disable PR trigger in release builds před 5 roky
examples 23c2202406 Support security descriptor string před 5 roky
src ea6cb8062a Remove strong name signing před 5 roky
.gitignore ea6cb8062a Remove strong name signing před 5 roky
CHANGELOG.md 26360ea696 Update documentation headers před 5 roky
CONTRIBUTING.md 2794d0d4b3 Initialize contributing guidelines před 5 roky
Directory.Build.props ea6cb8062a Remove strong name signing před 5 roky
Directory.Build.targets 31af6fe11c Remove dead codes před 5 roky
LICENSE.txt 5a6f3b9304 Update license for GitHub před 5 roky
MANIFEST.md f0ec34ba63 Clean up documentation před 5 roky
README.md dd33b0e639 Remove v1 from README před 5 roky
WinSW.nuspec 61e645e600 Merge pull request #452 from winsw/nuget-dotnet-461 před 5 roky
appveyor.yml 507674fbc1 Merge pull request #384 from NextTurn/config před 5 roky

README.md

winsw: Windows Service Wrapper in less restrictive license

Github All Releases NuGet Build Status Gitter License

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.

Why?

See the project manifest.

Download

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.

Usage

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 like start.
  • status to check the current status of the service.
    • This command prints one line to the console.
    • NonExistent indicates the service is not currently installed
    • Started to indicate the service is currently running
    • Stopped to indicate that the service is installed but not currently running.

Supported .NET versions

WinSW v2

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.

Documentation

User documentation:

Developer documentation:

Release lines

WinSW v2

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.

License

WinSW is licensed under the MIT license.