You need Visual Studio 2015 Update 1 to deploy and debug Universal Windows Platform Apps onto IoT-Core Build 10586, the Dec 3rd 2015 release. You MUST use Universal (Unencrypted Mode) authentication not NONE when Deploying/Debugging.

 

Part 2: Win 10–IoT Core- Visual Studio 2015 Update 1 App Deployment and Debug Requirement3-2

 

image

 

OK we have “lift off now” .. Phew!

I had seen the additional authentication mode, Universal (Unencrypted Mode) along with Windows and None. But I ignored it til now.! “Monkey on a typewriter” mantra should have told me its something new so give it a try!

 

As far as I can see this (as of time of writing this blog) is currently undocumented but is a must do.
Microsoft is updating the documentation to reflect this.

 

Fact: You need Visual Studio 2015 Update 1 to build apps for Windows 10 IoT-Core Build 10586 (as released publically on 3rd December 2015)

 

The Issue

In previous builds of the Windows 10 IoT-Core, MSVSMON was included in the image and running by default.  When you deployed/debugged an app from Visual Studio 2015 to IoT-Core device you set the authentication to NONE and your VS interacted with your device as a Remote Machine. With Build 10586, MSVSMON is not included in the image and so it needs to “bootstrapped” at deployment/debug. This means it is deployed before the app is downloaded each time. This change has been made because IoT-Core OS development kept running into issues as “Big Windows” evolved. IOT-Core leverages SSH to “bootstrap” MSVSMON  To perform this bootstrap NONE authentication can’t be used. You need Universal ( Unencrypted Protocol)..

 

Discussion

This is what I found:

  • You need to only use Universal (Unencrypted Mode) authentication method.
  • Two instances of MSVSMON run whilst you are running your app on the IOT-Core device
  • When you stop they stop.
  • If you then try to deploy/debug your app in None mode it fails
1>------ Build started: Project: App22, Configuration: Debug ARM ------

1>  App22 -> c:\users\david\documents\visual studio 2015\Projects\App22\App22\bin\ARM\Debug\App22.exe

2>------ Deploy started: Project: App22, Configuration: Debug ARM ------

2>Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named '192.168.0.28'.  The Visual Studio 2015 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.

========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
  • You can start MSVSMON in the debug tab of the web portal but deployment/debug with None Authentication fails:

Same messages as above

  • If you then try deploying using Universal (Unencrypted Mode) it fails you get the following:
1>------ Build started: Project: App22, Configuration: Debug ARM ------

1>  App22 -> c:\users\david\documents\visual studio 2015\Projects\App22\App22\bin\ARM\Debug\App22.exe

2>------ Deploy started: Project: App22, Configuration: Debug ARM ------

2>Error : DEP6953 : Failed to launch remote debugger with the following error: 'Command failed: 0x800705b4'.

========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
  • If you then stop the MSVSMON process in the web portal (you might have to X both instances) then you again can deploy/debug your app using Universal (Unencrypted Mode).

 

 

Note: The Start Visual Studio Debugger option in web-portal is only to be used for Console Applications as they do not support boot-strapping

 

Conclusions

 

Use Visual Studio 2015 Update 1 for app development with IoT-Core Build 10586.

The upshot is that you need always Universal (Unencrypted Mode) as your authentication mode whether the first or last deployment in a debugging session.

Ignore the “Start Visual Studio Debugger option on the Web Portal Debug.

Part 2: Win 10–IoT Core- Visual Studio 2015 Update 1 App Deployment and Debug Requirement3-2