Universal Windows apps
AppInstall can be used to install Appx packages on an IoT-Core device This blog covers an updated version of the toolkit for use on the latest Winsider IoT-Core builds.
Read the rest of entry »
After an absence from significant IoT-Core activity, whilst working on a significant phone app (as blogged here) I’m back in the IoT-Core space. Things have changed for the better so here goes. This blog covers my experiences with getting a RPI3 going with the latest Technical Preview build. Tools are now available to simplify setup and there is now a Remote Viewer. As a test UWP app, I have used (after a small modification) the Icons app on Codeplex, Universal Windows 10 SDK App Icons app as blogged in a previous blog. The app was modified because popups (as in MessageBox) are not supported in IoT-Core (Use thereof can cause an app crash in later OS versions). This feature change is covered.
Universal Windows(10) Apps settings is easy. Its simple to specify as part of the build, save them to storage, get them back and modify .. I mean dead easy!
I’m creating a Windows 10 Universal Phone App that talks to a Web Service to post an entity (object) in Microsoft SQL Server running on the same machine as the Web Service. Initially did all including the app on my laptop using localhost as the network target. Solved the SQL Server credentials .. OK. But when I switch to using the laptop’s system name or its IP address (all still running on same machine) got Network Access Required error.
In developing a Universal Windows app, when you add an existing XAML and its Codebehind page, they often end up unlinked in the Solution Explorer. This limits the ability to autogenrate event handlers in the codebehind page for UI elements.Spaso Lazarevic has a good solution that involves a little editing of the project file.
The previous blog explained what needs to be done to be able to deploy and debug apps with latest build for IoT-Core (Build 10586). On the Microsoft IoT forums it was reported by some that if they didn’t set up as in the previous blog they got a pin request. This blog provides some detail as to how the Universal (Unencrypted Mode) authentication works. It also explains why some got the PIN request.
This blog presents a Universal Windows App that connects to an embedded Bluetooth device over the Bluetooth Serial Profile using a genetic Bluetooth USB dongle. This app will run on both a Windows 10 IoT-Core devices such as a Raspberry PI2 and a Windows 10 Desktop. The blog covers in detail the key issues with pairing including where a passkey is required with a RPI2 as well as a Bluetooth primer. Update 1.2: One bug fix (was writing send text twice) and and one code improvement (menu returns DeviceInformation so no need to requery for it.)
Publ2shed on Codeplex and GitHub. More details later:Win10 IoT Core Universal Windows App runs on a Raspberry PI 2 (& desktop) that reads some sensors (on an Arduino board) saves to and from Azure Mobile Service
There are currently 2 reserved GPIO pins on the RPI2 that ordinarily are SOC (I call native) serial. A future Tx and Rx but not at the moment. Serial is achieved on the RPI2 with Win 10 IoT Core via a USB-Serial device connected to a Host USB port on the RPI2. There are though limitations in that the widely used FTDI chipset is not supported by Microsoft, although we have a solution. An alternative is over Bluetooth but there is an issue there.
The following is the complete Debug output for running the Startup Task. Two versions are shown. One with Managed Code Debugging and one with Native Code Debugging. Mixed is not permitted. An exception is thrown when the FTManager is instantiated. This error is not trapped by a Managed Code (c#) try-catch