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

HttpWebRequest support in CoreFX

We developed an HTTP and REST API library based on HttpWebRequest that's been working well for Unity games, but we're getting a lot of compilation errors when using CoreFX. Switching away from CoreFX results in compilation errors in HoloToolkit Spatial Mapping which uses asynchronous calls.

@DavidKlineMS Is there a way for us to avoid rewriting our HTTP layer while using CoreFX with HoloToolkit? Does it make sense to build our HTTP lib as a separate DLL and will it conflict with CoreFX when building the app for HoloLens?

Answers

  • Options

    @ContextVR in case it helps, this short video summarizes some of the advantages that you might gain from rewriting your HTTP layer for the Windows 10 platform.

    Windows Holographic User Group Redmond

    WinHUGR.org - - - - - - - - - - - - - - - - - - @WinHUGR
    WinHUGR YouTube Channel -- live streamed meetings

  • Options
    ContextVRContextVR ✭✭✭

    @HoloSheep Thanks, it would be interesting to find out exactly how much more optimized the new libraries are.

    Some familiar properties of HttpWebRequest (Timeout, KeepAlive, AllowAutoRedirect, etc) are now absent in NetCore, and I wanted to understand the reasons for such a drastic change.

    We now need to set headers manually to achieve HTTP output expected by the server, and still need to come up with new solutions for for other things (e.g. Timeout, KeepAlive).

    HttpClient might have everything for handling various HTTP scenarios, but before Unity/Mono catch up to the latest .NET, we'll need to maintain two different versions of the library for UWP and non-UWP Unity apps.

Sign In or Register to comment.