{"id":4212,"date":"2020-01-31T09:49:01","date_gmt":"2020-01-31T07:49:01","guid":{"rendered":"http:\/\/medtech-ingenieur.de\/?p=4212"},"modified":"2021-08-06T14:35:22","modified_gmt":"2021-08-06T13:35:22","slug":"uwp-app-packen-und-querladen","status":"publish","type":"post","link":"https:\/\/medtech-ingenieur.de\/en\/uwp-app-packen-und-querladen\/","title":{"rendered":"UWP app packaging and sideloading"},"content":{"rendered":"

This is a \u201cHello World!\u201d tutorial that explains how to package a UWP app and install it on another device.<\/p>\n

With UWP (Universal Windows Platform), Windows has provided APIs for many functionalities that are essential for wearable devices. For me, Bluetooth is the most important of these.
\nIn principle, these functionalities are also available in WPF applications, but with many Exceptions<\/a>. Therefore, I think it makes sense to implement GUI applications with functionalities like Bluetooth in the form of UWP apps.<\/p>\n

Even though the transition was a bit bumpy after extensive experience with WPF applications, I was able to get used to the basic idea of UWP apps. One stumbling block was creating an .exe for my UWP app. This isn't possible because the basic concept of apps is different. Apps are intended to be distributed via the Microsoft Store.
\nHowever, for development, it is necessary to create an executable file that can be run independently of Visual Studio without making it available in the Microsoft Store. To do this, the app must be packaged and then installed. Packaging and sideloading an app are here<\/a> As described. However, quite a bit more is shown, and I think a short \u201cHello World!\u201d for packing and sideloading is very helpful. I'm building on that here. \u201cHello World!\u201d<\/a> from Windows. After completing the steps described there, this article begins, explaining packaging and sideloading. Recipients of the app only need to complete steps 5 and 6.<\/p>\n

1. Create the app<\/h3>\n

Proceed as described in the \u201cHello World!\u201d<\/a> Article described.<\/p>\n

2. Create a certificate<\/h3>\n

For your app to be accepted as trusted, a certificate must be used. In our case, creating our own certificate is sufficient.
\nTo do this, open PowerShell (Windows + R and then type \u201cpowershell\u201d) and execute the following command, where the red<\/span> written parts should be adapted to your requirements:<\/p>\n

New-SelfSignedCertificate -Type Custom -Subject "CN=Hello World<\/span>, O=MedTech Engineer<\/span>, C=DE<\/span>"-KeyUsage DigitalSignature -FriendlyName"Hinrich Rahlfs<\/span>" -CertStoreLocation "Cert:\\CurrentUser\\My" -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.3", "2.5.29.19={text}")\r\n<\/pre>\n
\"Erstellen<\/a>
Creating the certificate in PowerShell<\/figcaption><\/figure>\n
For further information I recommend this link<\/a>.<\/p>\n
3. Customize the app manifest<\/h3>\n
Now Visual Studio needs to be informed about which certificate should be used.
\nTo do this, the app manifest must be opened in Solution Explorer.
\nSelect the \u201cPackaging\u201d menu item here.
\n\"Visuelle<\/a>
\nThen go to \u201cSelect certificate\u2026\u201d and then to \u201cSelect from store\u2026\u201d. In the dialog box that opens, you can now select the certificate you just created.
\n\"Dialog<\/p>\n
4. Packaging the app<\/h3>\n
Now everything is ready to package the app. To do this, right-click on the project in the Solution Explorer and select \u201cPublish\u201d (in older versions \u201cStore\u201d) \u2192 \u201cCreate App Packages\u2026\u201d.<\/p>\n