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.

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

Signed MixedRealityToolkit binary updates #1670

Merged
merged 10 commits into from
Feb 5, 2018

Conversation

keveleigh
Copy link
Contributor

@keveleigh keveleigh commented Jan 26, 2018

Overview

This is a new drop from https://github.com/Microsoft/MixedRealityToolkit, adding versioning info (starting at 1.0.0.1 for this drop) to all the DLLs and EXEs, as well as digitally signing the binaries with the official Microsoft certificate for authenticity.

The updated Sharing binaries will come from #1666.

In the future, drops will happen as necessary from the native repo, instead of all at once like this.

Changes

@keveleigh keveleigh self-assigned this Jan 26, 2018
StephenHodgson
StephenHodgson previously approved these changes Jan 26, 2018
@SimonDarksideJ
Copy link
Contributor

Quick Q @keveleigh , is there any advantage of updating these in the Dev Working Branch, when we already have them planned for the NameSpace Refactor? Which should merge soon.

@StephenHodgson
Copy link
Contributor

@DDReaper I think he just wants to verify they work

@keveleigh
Copy link
Contributor Author

when we already have them planned for the NameSpace Refactor?

I only have the sharing binaries planned to be updated in the namespace refactor branch. The rest can go directly into the dev branch, since there weren't any namespaces to be updated there.

StephenHodgson
StephenHodgson previously approved these changes Jan 26, 2018
Copy link
Contributor

@StephenHodgson StephenHodgson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested sharing service ✔️ (Tested in Namespace branch)
Tested Motion Controllers ✔️
Tested Plane Finding ✔️
Tested Spatial Understanding ✔️

@StephenHodgson
Copy link
Contributor

Will not including the ARM version of the Motion Controller prevent us from building for that platform target?

@keveleigh
Copy link
Contributor Author

The motion controller DLL is only used in the editor, while built apps call the platform API directly, so we don't need to ship any UWP versions of them.

@NeerajW NeerajW merged commit 0be77ff into microsoft:Dev_Working_Branch Feb 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants