VS 2015 support

[rvagg]

Continues on from #478 but against master this time

/R=@nodejs/platform-windows

[orangemocha]

Cherry-picking leftover... %nosnapshot_arg% should be %snapshot_arg%

[rvagg]

Thanks @orangemocha, decided that they belong in a separate commit rather than amending the cherry-pick

[orangemocha]

LGTM

[rvagg]

ran another CI against this and got this on win2008 only:

not ok 661 - test-timers-first-fire.js
#
#assert.js:89
#  throw new assert.AssertionError({
#        ^
#AssertionError: Timer fired early
#    at null._onTimeout (c:\workspace\iojs+pr+win\nodes\win2008r2\test\parallel\test-timers-first-fire.js:12:10)
#    at Timer.listOnTimeout (timers.js:89:15)
#timer fired in -0.6709120000000013

@Fishrock123 you're deep in timers now, does this fit into any existing context we have? I'm not sure if this has shown up before or not.

Merging regardless because this is unrelated.

[Fishrock123]

@rvagg Yes, that happens sometimes.

It's a minor bug somewhere very deep in windows libuv that will cause timers to occasionally fire quite early. Or something along those lines anyways. I think @orangemocha knew a bit more.

[benjamingr]

Hi sorry, I just got around to installing VS2015 on my desktop yesterday. Nice work!

[orangemocha]

It's a minor bug somewhere very deep in windows libuv that will cause timers to occasionally fire quite early. Or something along those lines anyways. I think @orangemocha knew a bit more.

Yes, that issue has been around for a while and that test is marked as flaky in joyent\node. nodejs/node-v0.x-archive#8960

We have been working on a fix (libuv/libuv#385), but it's still work in progress.