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

Add logic to know which SDK version we're targeting to better handle backwards compatibility #1289

Closed
2 tasks done
StephenHodgson opened this issue Nov 2, 2017 · 0 comments
Closed
2 tasks done

Add logic to know which SDK version we're targeting to better handle backwards compatibility #1289

StephenHodgson opened this issue Nov 2, 2017 · 0 comments

Comments

@StephenHodgson
Copy link
Contributor

StephenHodgson commented Nov 2, 2017 •
edited
Loading

Right now, Motion Controller visualizer depends on 16299 SDK calls that will prevent us from building for SDK targets less than 16299.

HoloLens OS is still 15063 14393.

Update
We will update the min SDK target to 16299 and update the scripts in the toolkit with Windows.Foundation.Metadata.ApiInformation API contract checks.

Affected scripts:

  • InteractionExtensions.cs
  • Build And Deploy Window
@StephenHodgson StephenHodgson mentioned this issue Nov 7, 2017
Merged
@StephenHodgson StephenHodgson mentioned this issue Apr 13, 2019
Merged
@StephenHodgson StephenHodgson changed the title Add logic to know which SDK version we're targeting to better handle backwards comparability Add logic to know which SDK version we're targeting to better handle backwards compatibility Apr 15, 2019
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
1 participant
@StephenHodgson