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.
Currently active Space and WorldAnchor store
I have started to experiment with persisting WorldAnchors.
I use my devices in a number of distinctly different locations on a regular basis, each being a different "Space" on the a device's Spaces list.
When I run my app with my experimental WorldAnchor persistence code at one location and then the other location and ultimately back at the first location, I have noticed that the WorldAnchor store does not seem to automagically map the store to the currently active Space. So I am guessing that I need to make unique id strings for each world anchor for each space, which will be easy to do if there is a way to make an api call to get the name or id of the currently active Space that the lens has resolved.
The apps in the shell seem to be Space aware. Does anyone know of an api call to get the currently active space? Is there some other way to make our world anchors space aware similar to the app placement in the shell?