* NuGet: Add simple NuGet packaging PoC
* Fix the version definition
* Run PS instead of CMD
* Fix the .NET4 binary reference in the spec
* Publish the NuGet package directly to the root
* Covert ID to uppercase just to follow the common notation
* Use a fixed artifact name to enable the deployment
* NuGet does not support multi-line paragraphs
* Add the NuGet badge
In order to maintain Release and Snapshot versions on AppVeyor, I had to create two separate jobs on it. These jobs utilise the same config, but actually they only specify different version formats.
* Release job: `2.0.{build}`
* Snapshot & PR builder: 2.0-SNAPSHOT-build{build}
Maybe it's not the best practice
* 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
