I mentioned in the last post I was going to try deploying our “Vacation Planner” web application to a Raspberry PI. I did try it and it did work. The web-app didn’t need any changes to run on the device. So while I don’t have a list of tweaks needed to make a webapp work on IOT devices I can tell you about some of the gotchas I encountered getting to the place where I could install the web-app.
If you are unfamiliar with the Windows UWP bridge it’s toolkit enables “you to quickly bring your existing applications to the Universal Windows Platform and Windows Store.” It wraps web-apps so you can deploy it to multiple devices (PCs, tablets, phones, HoloLens, Surface Hub, Xbox, and Raspberry Pi).
First thing is to get the win10 IOT operating system on to a sdcard for the Raspberry Pi to run. I already had a build from a couple of months ago but that became a major obstacle when an error told me the debugger version on the device did not match the version of VS on my dev machine. As of today the correct steps are listed here ms-iot.github.io/content/en-US/win10/SetupRPI.htm
With the OS on the sdcard the Raspberry Pi will boot up and grab an IP address over a wired network connection. No wifi support at this time, which is a big barrier for many who wont feel like running a long network cable through their house or office. I, myself, do not mind.
With the Pi on the network you can connect to it from your dev machine. Make sure the Windows Remote Management service is running on the dev system. For me it was off so I had to start it. I chose to have it always start automatically.
Scott Hanselman’s article is accurate for the commands to connect and login: hanselman.com/blog/SettingUpWindows10ForIoTOnYourRaspberryPi2.aspx.
Be aware that to the credentials for the Pi the username is “MINWINPC\administrator” and password is “p@ssw0rd” - some articles I saw did not have the machine name as part of the username in their instructions.
Scott had all the steps I needed except he was deploying a C# app which has a different manual config screen than what I needed for my remote web-app. For me when I selected the properties of my project it looked like this: In your setting choose not to use authentication. (shown here oliviaklose.com/hello-blinky/ )
The device is serving up a webpage that can be viewed at http://IP.AD.DRE.SS. Once you have deployed you will go to this webpage to START your app - using the webpage interface.
Heads up: The remote machine IP address setting can get stuck - I had to create a new app when the IP of my device changed.
Comments can happen here: /blog/issues/2[ Words: 528 ]