I would like to deploy a UWP package for enterprise. I have a Windows developer account but I don't want to publish it in Windows store or Enterprise store.
We have our URL to share the file, so the problem is when I try to install the Package in other PC the error 'Either you need a new certificate installed for this app package, or you need a new app package with trusted certificates' will occur.
Suggest the way to install it without publishing in store.
For your requirement, you could check Distribute LOB apps to enterprises document.
You have several options for distributing line of business (LOB) apps to your organization’s users using MSIX packages without making the apps broadly available to the public. You can use device management tools, configure an App Installer-based deployment, sideload the apps directly
And App Installer is suit for your scenario that double-clicking an .appinstaller file that installs the app package from a web server. For the detail steps you could refer to Installing Windows 10 apps from a web page document.
Related
I created an MSIX package for a WinForms desktop application using the Visual Studio Windows Application Packaging Project Wizzard with below settings:
sideloading, automatic updates enabled, installer location from url
I copied the package (all files) to a hosted website sub-folder (whose domain I own) but I do not know how to make the package available for installation on client desktops (i.e: give my clients a link to the package where they can start the installation). The package includes an Index.html which I tested by adding its url into the browser address field, but I got
The website cannot be reached
So I figured, that I need to host a small website with a download link that points to the Index.html.
But I wonder if there is a shorter/simpler approach - any help will be appreciated to point me to a more simple approach than hosting an entire website.
You need to leverage the appinstaller file built by Visual Studio next to your MSIX package.
In the linked article above we explain how the appinstaller file works with a small example.
Here are also more details about configuring auto-updates for sideloaded MSIX packages.
I want to add a desktop (WPF) application to the Windows Store using the Desktop Bridge (MakePri, MakeAppx). I have tested my build process using a self-sign certificate and all is well.
However, I cannot find any information stating whether I need an Extended Validation (EV) certificate or if an Organization validated (OV) certificate is sufficient. I know an OV certificate can cause SmartScreen warnings for installer .msi packages.
I also found old links (relating to Windows 8 apps) which say that the store does not use SmartScreen. But I cannot find anything relating to Windows 10 desktop apps packaged via the Desktop Bridge.
Will an OV certificate cause SmartScreen warnings when my converted application is downloaded from the store?
You don't need to use a valid certificate to publish your app to the Store. You just need to sign it with a test certificate. When you upload it to dev. center, it will be signed by Microsoft to be distributed through the Store.
I couldn't find a documentation that clarifies this, just saying it by my own experience. There are some notes here:
To test your app in a realistic setting as you prepare for
distribution, it's best to sign your app and then install it.
Visual Studio signs your app by using a test certificate. You'll find
that certificate in the output folder that the Create App Packages
wizard generates. The certificate file has the .cer extension and
you'll have to install that certificate into the Trusted Root
Certification Authorities store on the PC that you want to test your
app on.
Also if you use the new update of Visual Studio, you can create Desktop Bridge apps and publish them to the Store entirely through Visual Studio using the Windows Application Package project. It means you don't need to manually pack and sign it, VS does it for you.
Edit
Your users do not see an Smart Screen anyways. It makes sense since your app cannot run with administrator privileges. If your app needs a functionality that requires admin privileges, you need to consider it before moving forward.
I´ve developed a windows app with cordova/phonegap in visual studio.
I installed it for testing purposes with that instruction:
Cordova Visual Studio, install appx on windows tablet
Now, I want to install it on a few devices (Around 10) without publishing the app in the windows store.
With this instruction, I need a developer licence on each device. (and it is limited in time too)
Is there an other opportunity?
The recommended way is to perform bate app test. But you still need to publish it to the windows Dev center as described in this MSDN article.
For enterprise LOB apps, we can test it using Developer sideloading. But just as you've noticed, it requires developer licence on test device.
We have implemented a Windows 8 app. We tested the app by sideloading on both Windows 8.1 Pro and Enterprise. The app is working as expected when both the machines are connected to the domain. If both the machines are out of the domain, the app does not work and we receive the following error ‘This app can’t open. There’s a problem with app. Contact your system administrator about repairing or reinstalling it’. Also, in the event log the following error was displayed ‘Activation of the app 589f3680-7094-4066-92ee-75cd86b75bc1_5gyrq6psz227t!App for the Windows. Launch contract was blocked with error 0x80073CFC because its package is in state: Modified‘. We checked through on your sites and it is mentioned that Enterprise Sideloading key is mandatory for the app to work if the machine is not connected to the domain.
If we publish the app on Windows Store using ‘Targeted App Distribution’ method, do we still need to worry about the Enterprise Sideloading key or will the key be available when we will create a developer account on the Windows Center? Let us know.
Let us know if we are missing anything. Also, it will be helpful if you suggest any appropriate way as we need the Windows app to work without being connected to the domain.
Thanks
You could sideload the app if you have a developer license registered on the target machine. You can get a developer license via Visual Studio or with this powershell command:
Get-WindowsDeveloperLicense
However the developer license needs to be renewed every month.
See my answer here how to sideload an app:
sideload windows 8 apps to multiple devices?
I am developing a Windows 8 app (Modern UI) and I was asking if I could get the 'executable' of the app to install and test it in other computers without submitting the app to the market.
I am using the visual studio 2012 ultimate, if it helps.
Thank you in advance.
Right-click the project and choose Store - Create App Package and deselect uploading to the store. This will create a folder with the package for your app and all dependencies. Use the powershell script, which is also located in the folder to install the app. Normally if you run it for the first time it will probably ask you to change your ExecutionPolicy, but then it will install the app.
You can sideload an application on another machine without requiring the application be in the Windows Store.
One way, mentioned by Kai in another response to this question, leverages a developer license on the targeted machine. Because this mechanism uses a developer license it's not a suitable method for distributing apps for several reasons:
The license states "You may use the developer license only for the purpose of developing, testing and evaluating apps"
A developer license has a 30 (or 90 day) limit, after which the user will be re-prompted to renew the license; that's not a suitable experience for a 'finished' app.
Acquiring the license requires an internet connection, so the app may not start if offline.
The approved mechanism for distributing applications to the end-user outside of the Windows Store is via Windows 8 Enterprise or by purchasing enterprise side-loading activation keys for devices not running Enterprise (like RT). Some information on this process can be found here and here.