Build libuv with VS2017

[BrennanConroy]

BinSkim complains about some stack protectors when using VS2015 Update 2, its been fixed in VS2015 Update 3 or even better just use VS2017.

[moozzyk]

Building with VS2015 Update 2 is probably just a matter of updating VS on the agent(s). Building with VS2017 may require updating team city to be able to use latest MSBuild or changing MSBuild steps to cmd steps.

[muratg]

@natemcmaster do you think this will be a requirement with the new product build plans?

[natemcmaster]

Yes.

[natemcmaster]

Also, consider using cmake. The CoreCLR team uses this to build native code so it will be available in our product-build toolsets.

[muratg]

OK, assigning to @ryanbrandenburg, he can take a look when he's back. 🎁

cc @Eilon

[moozzyk]

I like the idea of using libuv's build system but I am not sure how feasible it is. I don't think they support building for windows arm (not sure about Linux). They also do not use CMake but gyp/autotools.