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.
Issue on debugging code in Holograms 101E
Hi there
We follow the instruction on Chapter 1 on https://developer.microsoft.com/en-us/windows/holographic/holograms_101e
When we open the generated code from unity into VS2015 and run, we have 25+ errors associated no object referenced ie:
UnityEngine.MonoBehaviour - The type of object is defined in assembly that is not referenced. You must add a reference to assembly 'System.Runtime, Version=4.0.20.0, ...
Any ideas what causing this?
Prior to this, we installed the prequisites software such as:
1. VS2015 Update 2
2. Hololens Emulator
3. Unity Hololens Technical Preview Beta 10 - 64 bits
4. UWP Runtime
Thanks
Best Answer
-
Isadewa ✭
Hi Jesse. Found what causing it. Apparently in our configuration on Nuget Package Manager, we untick for the Allow Nuget to download missing package; and Automatically check for missing package during build in VS. Once we tick back in and then we build one by one the solution and it works after that. Thanks
6
Answers
Hi Jesse. I don't think is that one cause **Build Failed ** straight away (set as Release > x86 >Hololens Emulator 10.0.11082.1039)
Hi Jesse. Found what causing it. Apparently in our configuration on Nuget Package Manager, we untick for the Allow Nuget to download missing package; and Automatically check for missing package during build in VS. Once we tick back in and then we build one by one the solution and it works after that. Thanks