Created a simple windows binary package.

`wasp start` fails at calling `npm` (can't find it).

appveyor.yml

@@ -41,19 +41,23 @@ test_script:
   - cmd: stack build --test # Run tests
 
 after_test:
-  - ps: mkdir appveyor-releases/
+  - ps: mkdir binary-package
-  - ps: mv "$(stack path --local-install-root)/bin/wasp.exe" "appveyor-releases/wasp-windows.exe"
+  - ps: mv "$(stack path --local-install-root)/bin/wasp.exe" binary-package/wasp-x86_64.exe
+  - ps: mv "$(stack path --project-root)/data" binary-package/data
+  - ps: mv tools/run_wasp.ps1 binary-package/wasp.ps1
 
 artifacts:
-  - path: waspc/appveyor-releases/wasp-windows.exe
+  # Since waspc\binary-package is a directory, AppVeyor will zip it for us and
-    name: wasp-windows.exe
+  # name it by the name of the artifact + .zip.
+  - path: waspc\binary-package
+    name: wasp-win-x86_64
 
 deploy:
   provider: GitHub
   auth_token:
     secure: kyc1YtELeuOSAvRQtg6ppmMWYkbsP16z3eBRu09YozknJEXySteOJTHUUyaMocjC
   description: "Automatic release"
-  artifact: wasp-windows.exe
+  artifact: wasp-win-x86_64
   force_update: true # Adds files to release even if it already exists.
   on:
     APPVEYOR_REPO_TAG: true # Deploy on tag push only.

waspc/tools/run_wasp.ps1

@@ -0,0 +1,2 @@
+$env:waspc_datadir="$PSScriptRoot\data"
+& "$PSScriptRoot\wasp-x86_64.exe" $args