Reputation: 71
Using Visual Studio 15.9.4, we are creating a UWP side-loading package. We are getting the new msix/msixbundle outputs.
Does anyone have any inputs on how to get UWP side-loading builds to work again?
Upvotes: 7
Views: 8153
Reputation: 827
I hit a similar issue because there are several steps to side-loading correctly. To that end I have wrapped it all up in an OpenSource batch file, which self elevates UAC so that it can enable dev mode/side loading, register the certificate file and then install the msixbundle or similar. It will then prompt the user if they want to create a desktop shortcut and lastly to launch the app after install.
The batch file can be found here, in a handy gist - https://gist.github.com/CartBlanche/cc135d46944818864d9d468916c982cd
Upvotes: 0
Reputation: 310
For anyone coming here from a google search, I was able to resolve a similar issue by installing the msixbundle via Powershell...
Add-AppPackage -path “C:\Caphyon\MyBundle.msixbundle”
Upvotes: 1
Reputation: 71
Ok, I am now experiencing stable behavior after upgrading my Windows OS to Version: 1809; Build: 17763.194.
Specifically:
I am able to install by double-clicking the msix/msixbundle from File Explorer.
I am able to run the Add-AppDevPackage.ps1 with PowerShell successfully.
Upvotes: 0
Reputation: 1086
After you successfully package the app with visual Studio, there will be a security certificate file in the form of .cer under the *_Test folder.You need to install the security certificate file before sideload your app.I often follow these steps to install the certificate: double click .cer file > choose Install certificate > choose Local machine > press the Browse button >choose Trusted Root Certification Authorities(or Trusted people)
We could run the .ps1 with PowerShell (if the device is the previous versions of Windows, you could refer the details on the document: Sideload your app on previous versions of Windows) or double click the appxbundle/msixbundle to install the app on the local device.
Upvotes: 2