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

VS and Unity Best Practices Article Suggestion

Re: https://developer.microsoft.com/en-us/windows/holographic/best_practices_for_working_with_unity_and_visual_studio

One tip I found on Unity's site was that you can expose fields in their editor via [SerializeField] attribute on a private field member, rather than wily-nily making items public that you'd rather keep encapsulated...while still allowing experiments in Play mode etc.

http://unity3d.com/learn/tutorials/modules/beginner/tips/private-variables-in-the-inspector?playlist=17114

Sign In or Register to comment.