Use Visual Studio 2017 15.4.5 instead of vs2017-15.7.4
@MarshallOfSound and @deepak1556 discovered that electron/electron#13618 was caused by the version of Visual Studio that we built with. This PR changes the master branch to use Visual Studio 2017 v15.4.5 which resolves the issue.
(cherry picked from commit ff3f2a71da778cd8c366b08681ba6b3f59b02606)
Use Visual Studio 2017 15.4.5 instead of vs2017-15.7.4 @MarshallOfSound and @deepak1556 discovered that electron/electron#13618 was caused by the version of Visual Studio that we built with. This PR changes the master branch to use Visual Studio 2017 v15.4.5 which resolves the issue. (cherry picked from commit ff3f2a71da778cd8c366b08681ba6b3f59b02606)