Hello everyone.

The Mixed Reality Forums here are no longer being used or maintained.

There are a few other places we would like to direct you to for support, both from Microsoft and from the community.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.

If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.

And always feel free to hit us up on Twitter @MxdRealityDev.
Options

What effect does setting the TargetDeviceFamily to Windows.Holographic have?

In the HoloLens academy they mention changing this line in the Package.appxmanifest file:

TargetDeviceFamily and change Name="Windows.Universal" to Name="Windows.Holographic".

Is this required or just recommended? And, what impact does it have?

Best Answer

Answers

  • Options

    Thanks @Waterine

  • Options

    @Waterine said:
    If you set TargetDeviceFamily to "Windows.Holographic" and submit the app to Windows Store, it won't be available for install on desktop or phone.

    An important clarification, it also won't be TESTED on desktop or phone. Many of us have been surprised that our first submitted app fails testing because it doesn't support touch.

    ===
    This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.

    (Daddy, what does 'now formatting drive C:' mean?)

Sign In or Register to comment.