Blog Park Client (Universal App) Development essay –app also need to pack before logistics

Think of a joke: Tang's monk a line of hardships came to the Buddha before, ready to learn, Buddha whispered asked a: Ru and so with a U disk? 4 people immediately fainted in the ground. All right, pull it off, just to tell everyone that the preparation must be in place.

The Universal app's packaging is not very different from the traditional Windows phone/windows Store app project, but given that there are always people who have problems with these steps, and even developers who have published several applications are no exception, So it is necessary to make a summary of this seemingly tedious process.

Pre-packaged preparations

1. Modify the compilation mode

When you debug a program, we usually choose Debug mode, but don't forget to switch to release mode when you publish, or the program won't execute even after it's packaged, let alone upload to the store. To ensure that the program runs on all devices, we select the any CPU so that our UAP runs on all available platforms (including the ARM-based Windows RT tablet and the x86-based tablet, such as Surface Pro).

2. Modify the Manifest file

The Manifest file records some of the underlying metadata in the project, including the project name, permission to apply, Logo and publisher information for the project, and so on, only if the information is complete and accurate, and the packaged file is guaranteed to be automatically verified at the time of uploading.

In the project we can find the Appxmanifest file for this project.

We can also find the entry to modify the Manifest file via the options in the menu.

Let's check to see if the contents of the Manifest file are complete individually.

In the Application tab, we need to fill in the basic information of the project and confirm whether we need to modify the corresponding screen rotation direction and how to notify the user when the lock screen.

Unlike Windows projects, the Windows Phone Project also requires users to fill in the option to allow the APP to be installed to the SD card.

In the Visual Assets tab, we need to use all the Logo image to do a good job, in general, if the name of the image in the Assets folder is correct, the image can be automatically loaded.

Note that the Badge Logo picture requirements are more stringent, the requirements can only be white and transparent two colors, even if there is a pixel in other colors, will be detected in the automatic verification program and do not pass, so when you modify these pictures must be careful to confirm that only contains white and transparent color.

On the capabilities page, we need to fill in the permissions for the project request, such as the project must be running under the network, so you must apply for Internet permissions. The key point to note is that any Windows App that requests network permissions must add an entry for the privacy Statement (Privacy Statement) in the Setting menu, otherwise it will not pass the manual approval phase. For information on how to add a privacy statement, please refer to the previous blog: Blog Park client (Universal App) Development Essay-Setting page implementation method and experience

The Windows Phone project also needs to fill in additional applications for device sensors, which need to be declared here if the app is applied to a gyroscope, magnetic field sensor, NFC, front/rear camera, and more.

In the Declarations tab, we want to declare the other resources used by the App, such as the blog Park project using the background task, you need to declare the portal of the background task here.

If the APP uses a special notification event that can be declared on the Content URIs page, it's important to note that Windows 8.1 supports only the HTTPS Protocol Security page and no longer supports the HTTP protocol.

The packaging page is critical, and any one of these errors will result in the project not being automatically audited at the time of uploading. Fortunately, most of the items in this page will be filled in automatically if we select the App that corresponds to the store in the steps below. And if we choose to just pack, entrust others to help publish, then this information must be completed. The information you need to fill out on this page can be found on the corresponding developer Account page.

Another consideration is the last Generate app bundle option. If always is selected, if the previous Visual Assets has a corresponding multiple-size picture, the package generates an entire package (bundle) of devices that correspond to multiple sizes. This will update the project later, you must upload a bundle, or you can not upload the audit. This also means that the images in the Assets folder can only be added and can no longer be reduced.

Of course all items above, we can right click on the manifest file, select View Code to modify or update. It seems that this is a more suitable method for geek.

Start packing

After the Manifest file has been modified, we can begin the formal packaging work.

Here we choose Create App Packages

Here, there are two options, select Yes to go directly to the Microsoft Dev account, bind the project and the App in the store, so that the information about the developer in the Manifest file is automatically updated to the corresponding information in the Microsoft Dev account. This approach applies to situations in which you publish your own projects.

Choose No to not login to the account, just pack. This applies when a third party is commissioned to help publish the project, or if you want to make a package for others to share as a test, you can submit the application directly with the test package, which is more consistent with the general workflow and avoids inconsistencies between your test package and the last-submitted store package.

We strongly recommend that you select No and use the second method. the next essay will detail how to submit an application.

Let's go to the Microsoft Dev account by selecting the first.

Once logged in, the developer's previously submitted projects are displayed, and we can also re-reserve a name for the new project.

Select the version information for the project, the output location, whether to package the build and CPU information.

Once you've filled it out, you're ready to package the project. When the package is complete, the project location is displayed, and the developer is reminded to perform the validator for the project (Windows APP certification Kit). Because after uploading the server will first perform this program for the initial automatic verification of the project, if there are irregularities in the place will not pass, so in order to ensure the success of the upload, we usually in the machine first to perform a verification program.

If the validator passes through the computer, you can upload the app to the store. Due to space limitations, we will continue to introduce store uploads in future articles.

Summarize

This article follows the process to describe the packaging steps of the Universal app before uploading the store, and analyzes the small differences between Windows and Windows Phone app packaging and the considerations that can lead to upload failures.

Our published apps and code can be found below:

Windows Phone Store App Link:

http://www.windowsphone.com/zh-cn/store/app/Blog Park-UAP/500F08F0-5BE8-4723-AFF9-A397BEEE52FC

Windows Store App Link:

http://apps.microsoft.com/windows/zh-cn/app/c76b99a0-9abd-4a4e-86f0-b29bfcc51059

GitHub Open Source Link:

Https://github.com/MS-UAP/cnblogs-UAP

MSDN Sample Code:

Https://code.msdn.microsoft.com/CNBlogs-Client-Universal-9c9692d1

Blog Park Client (Universal App) Development essay –app also need to pack before logistics