Introduction
The Windows Phone 8 Distribution model is different than iOS, Android and even Windows 10. This article documents how to submit a build successfully on this platform for processing.
The Procedure
Preparing Windows Phone 8 Builds for Distribution
The general process for creating and uploading a build is the following steps.
-
Obtain a Enterprise Mobile Signing Certificate from Symantec, $299/year. This only needs to be done once for the organization, not once for each app.
-
Use this certificate to create an Application Enrollment Token (AETX) file to be uploaded with the build.
-
Package the app for a non App Store deployment.
-
Sign the application with the same key used to create the AETX file.
-
Upload the AETX and Build file to the portal
Other helpful links for understanding Windows Phone distribution:
-
How to sign a company app store - https://msdn.microsoft.com/en-us/library/windows/apps/jj681686(v=vs.105).aspx
-
Company app distribution for windows phone - https://msdn.microsoft.com/en-us/library/windows/apps/jj206943(v=vs.105).aspx
-
Blog on company hub app - https://msdn.microsoft.com/en-us/magazine/dn296515.aspx
-
Blog on app signing and installation - http://blogs.msdn.com/b/jdupuy/archive/2013/03/11/windows-phone-8-company-hub-development.aspx
-
MSDN article on how to sign apps, what we are doing above - https://msdn.microsoft.com/en-us/library/windows/apps/dn168929(v=vs.105).aspx
-
Sideload Windows 10 apps: http://www.howtogeek.com/219651/windows-10-allows-you-to-sideload-universal-apps-just-like-android-does/
Packaging the Application
When using Microsoft Studio, you can package an app for App Store distribution or non App Store distribution. When bundling, or packing for the app store you'll end up creating an appx bundle.
While this is a valid build, it will prevent you from signing it in later steps. You must create an APPX file which then can be signed using the signing tool.
Application Properties
For convenience, configure your project to only create bundles when needed. Although you can choose a different option during the build process, this will make it easier and one less step to forget when building your application.
NOTE: For any of the pictures below, click on them to see a larger, more clear version.
Create App Packages
Once you are ready to upload your application to the platform, you can use the following steps to create the App Package (APPX) file.
NOTE: For any of the pictures below, click on them to see a larger, more clear version.
-
Ensure that either ARM or Neutral is selected for the Architecture and release model for that particular architecture is selected.
Signing the application
NOTE: For any of the pictures below, click on them to see a larger, more clear version.
Once the application is packaged, you must sign the application with the same private key used to create the AETX file in the earlier steps. Use the BuildMDILAPPX.ps1 to sign your application. Assuming your file is located:
powershell.exe –File “%ProgramFiles(x86)%\Microsoft SDKs\WindowsPhoneApp\v8.1\Tools\MDILXAPCompile\BuildMDILAPPX.ps1” -appxfilename c:\temp\AppPackages\«AppName»\«AppName».appx -pfxfilename C:\temp\«key file».p12 -password «password»
Parameter | Description |
---|---|
AppName | The name of your application, for example: App47.Test.WP81_1.1.0.9_ARM_Test |
key file | The name of the key file received when saving the certificate from Symantec, and the same one used to create the AETX file. Note, this does not need to live in the C:\temp directory, but does need to be available on your system where you are running this command. |
password | The password that was used when saving the private key file to your system. |
This will create a new updated appx file signed with your private key and certificate. Upload this appx file and your AETX file through the portal.
Comments
0 comments
Please sign in to leave a comment.