Hello everyone.

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.

Deploy HoloLens projects using IL2CPP instead of .NET

Hey Dev's
l'd like to know if and how it is possible to deploy to the HoloLens using the IL2CPP scripting backend with using the Build Window which is available in the current MRTK.
Since .NET is going to be deprecated in Unity 2018.2 it would be good to know how to get it running with the IL2CPP.

Cheers

CEO UniVRsitas

Best Answer

Answers

  • I am not sure about the build window but you can deploy to the Hololens using IL2CPP and Unity's build settings along with Visual Studio.

    Taqtile

  • Hey man, thanks for the info, will try it out.

    What is actually the big difference if you use IL2CPP or the .NET scripting backend for deploying to the HoloLens.

    Of course, eventually .NET will be deprecated but the BuildWindow which works fine with .NET really saves a lot of time.

    CEO UniVRsitas

  • One thing that I have found different between the scripting backends is that there is no need to tell unityscript to differentiate between unity_editor and uwp. I also found that you can use System namespace related operations and it will work on a UWP platform.

Sign In or Register to comment.