Grunt build to replace PS build

[BorisKozo]

Hi,

I have created a small POC of the more standard Grunt builder. You can check it out (pun intended) on this branch: https://github.com/BorisKozo/EndGate/tree/grunt_build

I also added the Grunt QUnit test runner so that the tests follow the sources properly. If you think this is the right direction I will edit the readme to include the new instructions and remove old build files.

There are couple of things I didn't understand.

1. _references.js file - why is it needed?
2. endgate.ts file - why is it needed?

I also don't know how to create a Nuget package but I will learn how to do it before I open a PR.

[NTaylorMullen]

So I took a look at your branch and left a few comments on your commit. Love the integrated QUnit tester, in the past I used Chutzpah but hey why not something new :). Lastly, after researching everything a bit more I think we should take a difference approach.

I don't think I want to "replace" the powershell build but instead utilize the grunt build if grunt is available, otherwise use powershell if its available. This way we can allow the most diversity in building EndGate source.

As for your questions:

1. The _references.js file is utilized by visual studio to allow project wide intellisense for any files referenced.
2. I just use it to build the endgate.d.ts file because it's put together in the correct order (left more detail in my comments on your commit).

Nuget package creation (how I do it now): https://github.com/NTaylorMullen/EndGate/blob/master/EndGate/build/Build.proj#L51-L61

Keep in mind that Build.proj file is run directly via the command line command ".\build BuildPackages" (while in the solution directory), I dont have it integrated with the regular build steps.