winsw/sign.sh

#!/bin/bash -ex
export "PATH=$PATH:/cygdrive/c/Program Files/Windows Kits/8.1/bin/x86"
for f in Release Debug;
do
  signtool sign /f winsw-key.snk /t http://timestamp.verisign.com/scripts/timestamp.dll bin/$f/winsw.exe
  signtool verify /v /pa bin/$f/winsw.exe
done
echo success
Visual Studio isn't signing bits for me. Just use the command line tool to get going. 2016-08-02 15:53:29 +00:00			`#!/bin/bash -ex`
			`export "PATH=$PATH:/cygdrive/c/Program Files/Windows Kits/8.1/bin/x86"`
			`for f in Release Debug;`
			`do`
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 08:34:19 +00:00			`signtool sign /f winsw-key.snk /t http://timestamp.verisign.com/scripts/timestamp.dll bin/$f/winsw.exe`
Visual Studio isn't signing bits for me. Just use the command line tool to get going. 2016-08-02 15:53:29 +00:00			`signtool verify /v /pa bin/$f/winsw.exe`
			`done`
			`echo success`