Visual Studio automatically creates a Test Certificate when the project is created. But in moving the code around, especially to and from a repository you might need to create a new one. Also, the default certificate that Visual Studio generates expires one year after the date on which the certificate was created. Before the certificate expires, you must use the App Manifest Designer to either regenerate the certificate or to create a new one. Without this you can’t create an AppX package for app installation. Here’s how to create a Test Certificate.
I purchased some Windows 10 Phones for business use where they are to run a custom UWP business app. Being about $100 they are quite economic but they were locked to local Telco, Optus (Australia). The Telco would give you the unlock key for $90 but I found an online site that could do it for about $20.
The key take home is that the instructions for implementing it as per the Telco and as per the source of the key I used, did not work for me but there is a simple method that worked for me that others had used with AT&T:
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!
It was simple enough to get access to a Microsoft SQL Server from a Web Service when all were running on the same machine. You use Windows Authentication. But when the services are both running locally, with the user running a Windows 10 Universal app that calls the web service, they won’t be logged in an so the web service needs credential for the SQL service.
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.
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.
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.
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.
Windows 10 desktop/tablet has undergone a major refresh. At the same time Windows Mobile (Windows Phone 10) has RTMed. Also Windows 10 IoT-Core has also invoked two license versions with its latest concurrent release.