We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
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.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. And always feel free to hit us up on Twitter @MxdRealityDev.
Emulator and localhost
I am trying to run one of our UWA solutions in the HoloLens emulator. Our app points to a service that is running in another instance of Visual Studio on my machine which is exposed to the UWA app over a localhost and port address.
The HoloLens emulator does not seem to be able to see localhost as it is configured out of the box. To confirm that it wasn't some other issue in our UWA app, I did a simple test and opened the Edge browser in the emulator and typed in the localhost:port address of the service (which also works from a browser). The Edge browser in the emulator threw a "Hmm, we can't reach this page." error, so I suspect that it has to do with the Hyper V VM configuration.
Is it possible to configure the Hyper V and the HoloLens emulator instance so that it can see localhost when debugging these kinds of solutions? If so, are there any simple instructions on how to make the necessary configuration changes?