Windows Phone 7 configuration file wmappmanifest. xml

Wmappmanifest. the XML file records the attributes of the application and defines the functionality of the application. If you open this file, will be roughly like the following content (the author only recorded part of the content)
<? XML version = "1.0" encoding = "UTF-8"?>

<Deployment xmlns = "http://schemas.microsoft.com/windowsphone/2009/deployment" appplatformversion = "7.0">
<App xmlns = "" productid = "{feff9099-9381-47fc-a91c-f64afe941b60}" Title = "inputscopedemo" runtimetype = "Silverlight" version = "1.0.0.0" genre = "apps. Normal"

Author = "inputscopedemo Author" Description = "sample description" publisher = "inputscopedemo">
<Iconpath isrelative = "true" isresource = "false"> applicationicon.png </iconpath>
<Capabilities>
<Capability name = "id_cap_gamerservices"/>
<Capability name = "id_cap_identity_device"/>
<Capability name = "id_cap_identity_user"/>
<Capability name = "id_cap_location"/>
<Capability name = "id_cap_medialib"/>
<Capability name = "id_cap_microphone"/>
<Capability name = "id_cap_networking"/>
<Capability name = "id_cap_phonedialer"/>
<Capability name = "id_cap_push_notification"/>
<Capability name = "id_cap_sensors"/>
<Capability name = "id_cap_webbrowsercomponent"/>
I believe you can also give a rough picture of the purpose of this file. At the beginning (the app tag Section) is a project-related attribute. The relevant descriptions are as follows:
• Productid: indicates the guid string list of the application.
• Runtimetype: Set the application to a Silverlight or xNa class.
• Title: The default name of the project. The text here is also displayed in the Application List.
• Type
• Version: version number of the application
• Genre: when the application is Silverlight, it will be apps. Normal, and apps. Game will be xNa.
• Author: Author name
• Description: Application description (description)
• Publisher: The default value is the project name. When your application uses push-related functions, this value must be

Next, the <capabilities> related blocks describe the functions that the application can use, such as whether the network function can be used or the media library content; in general,

We don't need to modify this part. Assume that when you remove some features, for example, you have removed the webbrowser part.
<Capability name = "id_cap_webbrowsercomponent"/>
When you use webbrowser-related functions in the Code, the program will fail, and the unhandle exception will directly close the application in Silverlight for Windows Phone.
Next, we can see the tag of the task, which is generally as follows:
<Tasks>
<Defaulttask name = "_ default" navigationpage = "mainpage. XAML"/>
</Tasks>
This is used inside the application and will not be modified in general. However, you can pay attention to the navigationpage section. If the name of your initial Page (the first page displayed) is not mainpage, you can make corresponding changes here.
Next is the part of the token, for example, the following
<Tokens>
<Primarytoken tokenid = "testtoken" taskname = "_ default">
<Templatetype5>
<Backgroundimageuri isrelative = "true" isresource = "false"> background.png </backgroundimageuri>
<Count> 0 </count>
<Title> test </title>
</Templatetype5>
</Primarytoken>
</Tokens>
Here, you can set the related settings after your application is added to the tile (that is, the home page; pay special attention to the setting of taskname, which is to start the related settings of the application after you run your application at the tile point, it corresponds to the name attribute in <tasks>.
Backgroundimageuri is the background pattern after your application is anchored to the home page (PIN to start). It will be clear from the following figure.

 
What is the purpose of the <count> label? Let's take a look at the effect. The following is the difference between count and count when count is set to 0 and count is set to 5.