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

Compatiblity of existing Win32 apps on hololens.

Hi,
I was porting my desktop app to UWP which was successful using
https://msdn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-manual-conversion

The appx file generated was running fine on Win10.
But when I tried to test on HoloLens emulator the deployment failed.
On going through the documentation
"https://developer.microsoft.com/en-us/windows/holographic/building_2d_apps"
I tried to change the TargetDeviceFamily in app.manifest to Windows.Universal but
there were errors that FullTrustApplication entry points are valid for UWP desktop applications.
Is there a way that I can convert the app to UWP universal so that it could run on HoloLens?

Answers

  • Options

    Wish I could move your question to the Questions category which is more generic.
    Anyway, there are probably many potential issues. From my own experience I found out that there are some things that could help:

    • The need to validate the APIs. The Desktop Windows 10 contains complete set of the APIs, but the HoloLens has much smaller version of the main OneCore APIs. That means that a Win10 desktop app can be build and work fine, but will fail on phone or HoloLens. Sometimes it is external libs that depend on "invalid" APIs which is hard, but if it is your own code, you can often find good alternatives. The tool is at:
      https://developer.microsoft.com/en-us/windows/develop/app-certification-kit
      The tool is usually run at submission time, but can be run at other times as well.

    • The TargetDeviceFamily probably should be "Windows.Holographic" unless your app can work well on desktop or Phone.

    • I think I initially also tried converting an existing solution into one for HoloLens UWP. It didn't go too well. What was easier was to create a new HoloLens templated solution and then add the the rest of my code as "Project". In fact I kept all my old "Win32" code as a static library targeting Windows 8.1. That is then linked to the main executable that is targeting Windows 10.

    • Be aware of any UI, file access, or any code that would require privileges that UWP apps don't have.

Sign In or Register to comment.