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

VS2017 failed to deploy to my hp mr

I created the holographic application using default vs2017 holographic template.But it failed to deploy to the device, the error message:"Deployment failed because no device was detected. Make sure a device is connected and powered on. [0x80131500]". But my mr device works correctly! I have also enabled develop mode. so what's wrong

Best Answer

  • Options
    yyaoyyao
    Answer ✓

    Yes, I have tried the local machine. VS 2017 default holographic template (both c# and c++) crashes. I have reported this question. And MS has marked it as VS bug.

Answers

  • Options
    Jimbohalo10Jimbohalo10 ✭✭✭
    edited November 2017

    You did not have the mixed reality portal running hence the error. You must be able to see the cliff room floor before deploying. In the headset get the desktop app running then click deploy to vs2017, from inside headset with mouse. Use local machine, device is for HoloLens
    see https://developer.microsoft.com/en-us/windows/mixed-reality/holograms_100 tutorials to mixed reality headset

  • Options
    yyaoyyao
    Answer ✓

    Yes, I have tried the local machine. VS 2017 default holographic template (both c# and c++) crashes. I have reported this question. And MS has marked it as VS bug.

Sign In or Register to comment.