Forum Discussion
Question about sharing an App being developed without deployment
Hi. I am currently developing a Hololens 2 App with VS2019 + Unity + MRTK.
I test the App being developed by deploying it to Hololens 2 with VS 2019, but I'd like to let my team member who is not a programmer and works at a distant place also test it. Is there any way to let him install the App (via packaging and etc. ) to his Hololens 2 without the deployment process via VS2019?
You're probably looking to create a .appx file! Here's how you create one of those.
For installing an .appx, you'll need either the device portal, or Visual Studio again. There's a short doc on that over here. The device portal does still have a bit of a setup, but it should be much easier than Visual Studio!Hope that helps ๐
- Ramorake63Copper Contributor
Sharing your Holo lens 2 app without using the deployment process in Visual Studio can be achieved by creating an app package. You can use Unity to generate a build, then package the app using Visual Studio as a standalone installer. Once packaged, you can share it with your team member to side load onto their Hololens 2 device. Make sure they enable Developer Mode on their device to allow side loading.
By the way, while you're exploring innovative apps, why not take a break with a fun game like 3 Patti Blue https://3pattiblueapk.pk/It's an exciting card game thatโs perfect for unwinding!
- koujakuMicrosoft
You're probably looking to create a .appx file! Here's how you create one of those.
For installing an .appx, you'll need either the device portal, or Visual Studio again. There's a short doc on that over here. The device portal does still have a bit of a setup, but it should be much easier than Visual Studio!Hope that helps ๐
- robobegCopper Contributor
koujaku Thanks a lot. I tried as you advised and succeeded in packaging & installing the app. The app was not able to open '.xml' files but I found that I didn't provide necessary attributes such as 'FileAccess.Read'. ( But weirdly the app was able to open them when deployed via VS2019. )
Thanks, again!