github
/
winsw
mirror of https://github.com/winsw/winsw
1
0
Fork 0
Code Issues Releases Wiki Activity
230 Commits
12 Branches
43 Tags
5 MiB
C# 99.6%
JavaScript 0.4%
 
 
Go to file
Oleg Nenashev 6c0f6d1f7a Fixes #142 - Deploy the automatic build on Appveyor (#144) 
* First configuration stub

* Get rid of the old winsw_cert.pfx references, adjust docs

* Fix the corrupted log4net reference, we use 2.0.3

* Generate stub SNK file

* Signing: Try full SDK path to generate SNKs

* Fix the path

* Signing: Sign all assemblies being packed into WinSW

* Tests: Try enabling tests

* Tests and artifacts: Use absolute paths

* Artifact path must be relative

* The test DLL is the NUnit one

* nunit-console does not require loggers

* NUnit: Try picking all DLLs in the output folder

* NUnit console: No wildcards

* Tests: Fix the test project to make it properly working with the new project structure

* Docs: Clarify the specifics of external extension usage

* Add AppVeyor badge to README.md
 		2016-12-04 09:34:19 +01:00
doc Fixes #142 - Deploy the automatic build on Appveyor (#144) 2016-12-04 09:34:19 +01:00
packages Add "version" and "help", handle unsupported commands (PR #81) 2015-02-03 00:05:56 +03:00
src Fixes #142 - Deploy the automatic build on Appveyor (#144) 2016-12-04 09:34:19 +01:00
.gitignore Fixes #142 - Deploy the automatic build on Appveyor (#144) 2016-12-04 09:34:19 +01:00
CHANGELOG.md Document the extension engine and exisitng extensions (#141) 2016-12-02 13:59:26 +01: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 Fixes #142 - Deploy the automatic build on Appveyor (#144) 2016-12-04 09:34:19 +01:00
appveyor.yml Fixes #142 - Deploy the automatic build on Appveyor (#144) 2016-12-04 09:34:19 +01:00
sign.sh Fixes #142 - Deploy the automatic build on Appveyor (#144) 2016-12-04 09:34:19 +01:00
winsw.csproj Fixes #142 - Deploy the automatic build on Appveyor (#144) 2016-12-04 09:34:19 +01:00

README.md

winsw: Windows service wrapper in less restrictive license

Build status

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:

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-key.snk should be available in the project's root in order to build the executable
  • You can generate the certificate in "Project Settings/Signing"
  • The certificate is in .gitignore list. Please do not add it to the repository