v1.2.6: Fix and simplify custom gatekeeper to handle a normal 'npm pack' tgz …

Improved custom gatekeeper process to use a normal 'npm pack' file instead of the custom zip file. Process improvements specially related the installation of a 'dev' gatekeeper

v1.2.5

New property to bypass dependencies installation

v1.2.4

Fixed stop windows service not working (Issue #6 )

v1.2.3

Fixed Issue #3 and Issue #5

v1.2.2

Fixed Issue #2 and Issue #4
Added feedback on the checks, better exit codes, better exit handling and interactive vs non-interactive improvements.

v1.2.1

Fixed issue that re-installation would fail when new updates for vs build tools were available.
Added set folder permissions for the enabling only the access of the current user and the installServiceAs user.
Cleanup and improvement of error handling for the dependencies.

v1.2.0

Changed from npm windows-build-tools to more controlled and user friendly installation.
Added uninstall (beta)
Added InstallationFolder to allow installation of everything on a custom folder
Added InstallServiceAs to allow installation of service as localsystem, localservice or networkservice (permissions on InstallationFolder need to be set by hand in this cases so that the service can access)
Bugfixes and cleanup

v1.1.0

Fix for zip file

v1.0.0

Initial release
Installs beame gatekeeper or beame sdk and their dependencies on a windows 64bits computer (tested with windows server 2012 and 2016)
In case of beame gatekeeper it also allows pre configuration of gatekeeper settings, support for custom gatekeeper and custom css, installing it as a windows service, configuration of system proxy, etc