Build Portal Updates

[StephenHodgson]

Overview

• Added quick options to switching between Immersive Head Mounted Displays (IMHDs) and HoloLens
• Manually add IP of remote devices
• Install via WiFi
• Better enumeration of Appx Package folders. Fixes build discovery #1136
• Fixed Build window incrementing the reserved number for Windows Store Apps Build window increments the reserved number for Windows Store Apps #1402
• Add support for installing on local machine (for IMHD apps)
• HTTPS support Build window to support HTTPS communication #98

Changes

• Fixes: Update BuildAndDeployPortal #1020
• Fixes: Build window to support HTTPS communication #98
• Fixes: Build window increments the reserved number for Windows Store Apps #1402
• Fixes: APPX does not build on current Unity Version (Assembly-CSharp-firstpass does not exist) #1424
• Fixes: HoloToolKit.Unity.XdeGuestLocator - Failed to locate internal switch adapter  #1519

[SimonDarksideJ]

Found 1 issue.
If I add a new machine on the Deploy options and then select Local Machine. The "Open Device Portal" button is still enabled. Which doesn't work as it points to 0.0.0.0?

Although in fairness, this should be available and point to https://localhost:50443

Thoughts @StephenHodgson ?

[StephenHodgson]

Well, if you select local machine, then the active IP is the local one. But I should look at cleaning that up if the address isn't properly filled out.

Under the hood if the address is invalid, it doesn't do anything anyway.

Does the 50443 port number have any special significance?

[SimonDarksideJ]

50443 is the default port assigned for Immersive Headsets I guess. Unless the port is totally random, in which case you'll need to make it configurable on the screen. Best to get a few to test and report their ports

[StephenHodgson]

Why would you need to add an immersive headset to the machine options?
The local machine is the one for a local build with the immersive headsets, and it installs and runs the appx via powershell.

[SimonDarksideJ]

Because the Device Portal is a general device portal and also works for immersive headsets :D

[StephenHodgson]

I'm confused. Why do you need the device portal for a local PC machine though?
You just run, install, and do what you need right in the environment you're in.

[StephenHodgson]

The Build window already handles everything you need to do for the local machine. No device portal required.

[SimonDarksideJ]

Ok, fair enough. Only thought Immersive / Local machine users might find easy access to the device portal useful as well. If we're not supporting that, then just ensure the button is only enabled for IP / HL targets :D

[StephenHodgson]

If we're not supporting that, then just ensure the button is only enabled for IP / HL targets :D

I believe it should get disabled if there isn't a HoloLens detected. Let me know if this isn't the case.

[NeerajW]

@DDReaper added you as moderator. Please accept invite.
Appreciate your review here.