Go to file
Oleg Nenashev e69957824b Docs: Update LICENCE.txt, mention other contributors 2016-11-26 01:41:07 +03:00
doc Docs: Cleanup leftover TODOs 2016-11-26 01:40:02 +03:00
packages Add "version" and "help", handle unsupported commands (PR #81) 2015-02-03 00:05:56 +03:00
src Merge branch 'master' into winsw-2.0 2016-11-10 13:25:42 +01:00
.gitignore Strong name signing of merged assemblies. 2015-02-08 14:28:16 +03:00
CHANGELOG.md Docs: Add changelog 2016-11-26 00:00:30 +03:00
LICENSE.txt Docs: Update LICENCE.txt, mention other contributors 2016-11-26 01:41:07 +03:00
MANIFEST.md Docs: Decouple the project manifest to a standalone page 2016-11-26 01:28:42 +03:00
README.md Add a simple documentation stub for the EXE Config File 2016-11-26 01:36:39 +03:00
sign.sh Visual Studio isn't signing bits for me. 2016-08-02 08:53:51 -07:00
winsw.csproj Visual Studio isn't signing bits for me. 2016-08-02 08:53:51 -07:00

README.md

winsw: Windows service wrapper in less restrictive 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

Right now the project uses Jenkins Maven repository as a main storage of release files. Binaries are available here.

Some releases (e.g. alpha- and beta-versions) can be also downloaded from the project's GitHub page. This source of releases is not an official one.

Usage

WinSW is being managed by configuration files: Main XML Configuration file and EXE Config 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 to indicate the service is not currently installed, Started to indicate the service is currently running, and Stopped to indicate that the service is installed but not currently running.

Documentation

Release lines

WinSW 2.x

This is a new release line under active development. API stability is not guaranteed till the first release, the project structure is in flux.

Major changes since 1.x:

  • Rework of the project structure
  • Better logging
  • Internal plugin engine, which allows extending the WinSW behavior

WinSW 1.x

This is an old baseline of WinSW. Currently it is in the maintenance-only state. New versions with fixes may be released on-demand.

Build Environment

  • IDE: Visual Studio Community 2013 (free for open-source projects)
  • winsw_cert.pfx should be available in the project's root
  • You can generate the certificate in "Project Settings/Signing"
  • The certificate is in .gitignore list. Please do not add it to the repository