I developed an Windows 10 UWP Application. This application should be used in the company, so I build it via the built in tool of Visual Studio 2015.
To do that i followed this guide : Packaging Universal Windows apps for Windows 10
This worked fine, and i don't have a problem to install the Add-AppDevPackage.ps1 via Windows Powershell when i have the "developer mode" enabled.
Now the problem:
I don't want that my employees have to activate the developer mode. They should activate the "sideload applications" option. When this option is checked the shell allways asks me to activate the developer mode and fails if I don't activate it.
So what do I have to do, that it is enough to activate the "sideload applications" option to install my developed application?
When I built the apppackage i checked the following settings:
Do you want to build packages to upload to the Windows Store?
==> No
Generate app bundle ==> Always
Sideload apps is a more secure option than Developer mode because you cannot install apps on the device without a trusted certificate.
Requirements
Here's what you'll need to have:
Devices need to be unlocked for sideloading (unlock policy enabled)
Certificate assigned to app
Signed app package
And here's what you'll need to do:
Turn on sideloading - you can push a policy with an MDM provider, or
you can use Settings.
Trust the app - import the security certificate to the local device.
Install the app - use PowerShell to install the app package
How do you sideload an app on desktop
You can sideload apps on managed or unmanaged devices.
To turn on sideloading for managed devices
Deploy an enterprise policy.
To turn on sideloading for unmanaged devices
Open Settings.
Click Update & Security > For developers.
On Use developer features, select Sideload apps.
To import the security certificate
Open the security certificate for the appx package, and select
Install Certificate.
On the Certificate Import Wizard, select Local Machine.
Import the certificate to the Trusted Root Certification Authorities
folder.
To install the app
From the folder with the appx package, run the PowerShell
Add-AppxPackage command to install the appx package.
Source: https://technet.microsoft.com/itpro/windows/deploy/sideload-apps-in-windows-10
Related
So, we finished a few wpf conversions to .net core, and now we have a need to ship one to an external client as an installer. Previously we used ClickOnce, but that has been deprecated in .net core and will not be ported according to MS, with them recommending MSIX. However, as we understood from docs, even though we'll sideload a WPF application it will still run in a sandbox with a virtualized file system. And that is a no go for us, it has obviously been designed with UWP+Marketplace delivery in mind. We need the application on the file system with full access to file system, the "good old way".
We could just ship them as a zip file and have the client unpack, but management deemed that as not-so-professional, so we need a delivery package similar to what msi/clickonce had. Has anyone delivered apps on core outside MSIX?
EDIT: Microsoft has announced they are going to include ClickOnce support in .NET 5
You can deploy .NET Core and .NET 5 applications internally in an organization by sideloading msix packages.
I have been successfully using Clickonce for deploying .NET line of business applications for years.
Now that I’m updating my apps to .NET Core I wanted something similar to Clickonce. In other words: publishing your installer in a network share and deploying your autoupdating app to your clients by simply coping a shortcut to your installer.
You can achieve this with msix packages. The problem is that you are limited to Windows 10 version 1709, and later
The solution came on December 19th with MSIX Core 1.1. Packaging your app with msix core support you can target Windows 7 SP1 and later, and this is something I needed because at work we are slowly transitioning to Windows 10 from Windows 7 and I still have to support old versions of windows.
The steps for packaging your .net core app using msix core are:
Create a Windows application packaging project in your solution.
Right click on the Applications subfolder of your Windows application packaging project and select Add Reference. Then select your target project.
Change your Package.manifest (reference: msix-packaging/MsixCore at master · microsoft/msix-packaging · GitHub) Right click your Package.manifest file and select View code Change your to:
<Dependencies>
<TargetDeviceFamily Name="MSIXCore.Desktop" MinVersion="6.1.7601.0" MaxVersionTested="10.0.10240.0" />
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.16299.0" MaxVersionTested="10.0.18362.0" />
</Dependencies>
With this you stablish your min version to MSIXCore.Desktop in other words Windows 7 sp1.
Right click your Windows application packaging project and select Publish then Create App Packages.
Choose Sideloading then check Enable automatic updates.
In order to install the package in the client machine you must sign it. I recommend you to create a self-signed certificate. You must install the certificate in the client machine so that the package is trusted and you can install it. If you are in a domain you can deploy your self-signed certificate with a group policy.
The optimal situation is to sign the package with a trusted certificate provided by a trusted root certification authority. My personal choice is to create a certificate in my own windows certification authority (which is trusted in my local domain). If you decide to sign your package with a trusted cert this is the command line:
.\SignTool.exe sign /fd SHA256 /a /f yourcert.pfx /p yourpassword *.appx
Select Generate app bundle to Never.
Select your network share for publishing the package
In order to execute your package installer in Windows 7 sp1 machines you must previously install msixmgrSetup-1.1.0.0-x64.msi or msixmgrSetup-1.1.0.0-x86.msi accordingly. You can find the installer here
Windows 10 machines will recognize the installer right away.
If you want to know more about msix packages you have a good explanation here
I hope this guide helps you to get your deployment system working.
Well, apparently, we are again faced with "our way or the highway" from MS, so we just used Inno Setup. Until such time we get a proper installation process or MSIX allows unsandboxed setup without unnecessary file system abstraction, this will have to do.
There are other tools such as Advanced Installer or InstallShield that can create a MSI/EXE installer now and later in case you decide to go with the MSIX, you will just add a new build to your current project.
The tool will automatically sync the content of the MSI with the MSIX, or at least this is what Advanced Installer does for you.
They also have a VS Extension, so you can build the installer inside your Visual Studio IDE.
So I am building a test application using the basic Vuforia implementation in Unity for export to UWP (universal windows platform). I am running into issues when trying to install the packaged application on computers other than the one I developed it on.
When running the installer I get an error after initializing the install from the packaged .appx file:
I run the installer on the computer that I built the unity application on, the installer works fine, it installs the application and runs perfectly and builds without errors.
However, when I try to move the .appx by itself to another computer and install it there, it is giving me this error on all computers I try.
"App Installer failed to install package dependencies. Ask the developer for Microsoft.NET.CoreRuntime.1.1 package."
I tried to install the .NET.CoreRuntime.1.1 package with no avail from the .NET Downloads page
FYI - the .appx file generated is the "Release" version for x64.
What am I missing here? How can I include the dependencies in the .appx file itself?
What am I missing here? How can I include the dependencies in the .appx file itself?
The Microsoft.NET.CoreRuntime.1.1 could not be Integrated into the app package directly. You need to install the dependencies package separately before install the app.
The store will install package dependencies to your machine automatically when install the app with Microsoft Store. So you could publish your dependent package to the store.
If you only want to install the app through the sideloading, you could make PowerShell command to install the package dependencies in the Dependencies folder where under the appx folder.
For Windows 10 Fall Creators Update, related sets can now be installed via App Installer. This allows distribution and deployment of related set app packages to users. And this is documentation you could refer to.
I wanna Publishing .IPA,This step is success,but I cant install in my Iphone via Xcode,that show :
BTW, I can use Xcode with Swift publish .IPA ,and success install it,
but I'm must use Xamarin.
Thanks!
For publishing your application on App store, you need to sign the application using distribution provisioning profile and certificate. By using distribution provisioning profile you can't install your application on device.
If you need to install your application on device please use the development provisioning profile and certificate to sign the application.
For further reference please visit -
XCode 8 A valid provisioning profile for this executable was not found
So, my team and I are developing an app but we don't have a code signing certificate for multiple reasons. We are using the Universal Windows blank app template, so the result is an .appxbundle. I thought I could deploy it like any other program, without a Code Signing Certificate, but I can't figure out how to do that, is it possible?
PS: using Universal Windows template for W10 on VS2017.
Thanks in advance and tell me if you don't understand,
RektibouCaribou
If you have generated package file successfully.
you can sideload apps to your device without submitting them to the Store. This lets you install them and test them out using the app package (.appx) that you have created. If you have an app that you don’t want to sell in the Store, like a line-of-business (LOB) app, you can sideload that app so that other users in your company can use it.
MSDN source:Sideload your app package
we need to install a windows store app on a windows 10 LTSB.
Is it somehow possible to legally get an appx package of a store app so we can install it or are there some other ways to do it?
If you go to Settings > Updates and Security > For Developers Go to Use Developer features and select Sideload apps.
Then you will need to install the certificate for the application, This will be bundled with you appx package. Import the certificate to the local machine under the Trusted Root Certification Authorities folder.
Finally, sideload your app onto the machine using Powershell and the Add-AppxPackage cmdlet.
You will now have the application installed on that Windows 10 Machine.
EDIT:
I notice you are wanting to install an app you havent created, already on the app store, following these steps had some success to get apps running on LTSB version of Wiindows 10.
As from http://answers.microsoft.com/en-us/windows/forum/windows_10-start/windows-10-enterprise-ltsb-no-more-built-in-metro/ab8dbbe5-ef56-47c0-98a0-4a9a7d9763b8?auth=1
Grab C:\Program Files\WindowsApps from Install.WIM on a Windows 10
Enterprise CB ISO
Place them as you see them in the WIM on your real system
Add-AppXPackage -Register 'C:\Program
Files\WindowsApps*\AppManifest.xml' -DisableDevelopmentMode
(Repeat the last step 2 more times to work around dependency hell)
Do as this article tells you to do:
https://support.microsoft.com/en-us/kb/2798317