WinSW 3 can run on Windows platforms with .NET Framework 4.6.1 or later versions installed. For systems without .NET Framework, the project provides native 64-bit and 32-bit executables based on .NET 7.

More executables can be added upon request.

.NET Framework system requirements
Preinstalled since Windows 10, version 1511 and Windows Server 2016.
Installable since Windows 7 SP1 and Windows Server 2008 R2 SP1.

.NET 7 system requirements
Supported since Windows 10, version 1607, Windows Server (Core) 2012 R2 and Nano Server, version 1809.

Latest release and pre-release WinSW binaries are available on GitHub Releases.

Alternative sources:

• CI builds are available on Azure Pipelines.

• NuGet. (2.x)

• Maven packaging for executables, hosted by the Jenkins project. Binaries are available here. (2.x)

1. Take WinSW.exe or WinSW.zip from the distribution.

2. Write myapp.xml (see the XML config file specification and samples for more details).

3. Run winsw install myapp.xml [options] to install the service.

4. Run winsw start myapp.xml to start the service.

5. Run winsw status myapp.xml to see if your service is up and running.

1. Take WinSW.exe or WinSW.zip from the distribution, and rename the .exe to your taste (such as myapp.exe).

2. Write myapp.xml (see the XML config file specification and samples for more details).

3. Place those two files side by side, because that's how WinSW discovers its co-related configuration.

4. Run myapp.exe install [options] to install the service.

5. Run myapp.exe start to start the service.

You write the configuration file that defines your service. The example below is a primitive example being used in the Jenkins project:

<service>
  <id>jenkins</id>
  <name>Jenkins</name>
  <description>This service runs Jenkins continuous integration system.</description>
  <env name="JENKINS_HOME" value="%BASE%"/>
  <executable>java</executable>
  <arguments>-Xrs -Xmx256m -jar "%BASE%\jenkins.war" --httpPort=8080</arguments>
  <log mode="roll"></log>
</service>

The full specification of the configuration file is available here. You can find more samples here.

WinSW is being managed by the XML configuration file.

Your renamed WinSW.exe binary also accepts the following commands:

Experimental commands:

Most commands require Administrator privileges to execute. WinSW will prompt for UAC in non-elevated sessions.

• Migrate to WinSW 3.x

• Configuration:

• XML configuration file

• Logging and error reporting

• Extensions

• Use cases:

• Self-restarting services

• Deferred file operations

• Troubleshooting

【版权声明】
本站部分内容来源于互联网，本站不拥有所有权，不承担相关法律责任。如果发现本站有侵权的内容，欢迎发送邮件至masing@13sy.com 举报，并提供相关证据，一经查实，本站将立刻删除涉嫌侵权内容。