Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade to current Windows 10 SDK: v16299 #150

Closed
FunctionPoint opened this issue Jan 7, 2018 · 2 comments
Closed

Upgrade to current Windows 10 SDK: v16299 #150

FunctionPoint opened this issue Jan 7, 2018 · 2 comments

Comments

@FunctionPoint
Copy link
Contributor

The current VM is targeted towards: v15063.
@blairmcg
Copy link
Contributor

blairmcg commented Jan 8, 2018

If there is a compelling reason to do this (e.g. desire to use a new API), but otherwise I don't think we should unless v16299 is the default for new installations of VS2017. Otherwise it forces everyone to have to go and install the new SDK without any particular upside.
Its reasonable to keep this issue around, however, until the reason or reasons arise.

@blairmcg
Copy link
Contributor

blairmcg commented May 9, 2018

The 7.1 branch is now targeting v17134.0. I don't think it is worth changing the 7.0 build.

@blairmcg blairmcg closed this as completed May 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FunctionPoint @blairmcg