In previous versions of IoT-Core, you just used the Authentication Mode-None when deploying and debugging an app from Visual Studio. This has changed a little so this blog is just a short note about the configuration for deploying a Universal Windows App from Visual Studio to an Windows 10 IoT-Core device.


Hey I’m back Smile
Ok its been awhile since I last blogged. Apart from the festive season, I’ve been busy with a real phone app for a client. More about that in my next blog.


My System

OS Name: Microsoft Windows 10 Pro Insider Preview (Fast Track)
Version: 10.0.11099 Build 11099  10.0.11102 Build 11102 (My system upgraded overnight!)

Microsoft .NET Framework Version: 4.6.01038

Visual Studio Enterprise 2015
        Update 1, Version 14.0.24720.00 Update 1

Debugging Tools for Windows   10.0.10011.16384
Visual Studio Tools for Universal Windows Apps   14.0.24720.00


Target  Systems

Raspberry Pi 2 , Qualcomm DragonBoard 410c MinnowBoard Max (I haven’t got one of these yet)  etc (There are others such as the Toradex Colibri T30)

Windows 10 IoT-Core
Build/ OS Version: 10.0.10586


Visual Studio 2015 IoT-Core Debug Setup

As mentioned above you just set the Authentication to None on the Debug tab of a Windows Universal project properties sheet, along with the target’s IP address. You then can deploy and debug a UWP app on a device.



This has now changed. You have two options:


(A) Instead of None use Universal(Unencrypted Protocol) for the authentication



(B) Run the web portal (http://<Device IP Address>:8080 ) in a web browser.
      Go to the Debug Tab and press Start Visual Studio Debugger:


     A Dialog box will appear saying use <Your device’s IP address> <A TCPIP Port>  (eg. as the Remote Machine Name in Visual Studio Debug setup


You use that IP:Port along with Authentication-None:



PS: So is Port 8116 just the Universal Unencrypted Protocol Port?

I tried rebooting and just using the (B) configuration without starting the debugger; no dice.

I tried suing the Universal Unencrypted Protocol after starting the debugger on the device.
You get  Failed to launch remote debugger with the following error: 'Command failed: 0x800705b4'
I couldn't see any global assignment of port 8116.

My conclusions are:

  • Unlike previous versions, the debugger is not running by default on IoT-Core devices
  • You can start it as in (B) then do an open download/debug.
  • Or use Universal Unencrypted Protocol as in (A) which will attempt to start the debugger each time over SSH.

Hope this helps. Please leave a comment if it does, thx