Application Submission Requirements
May 16, 2012
The following requirements are validated during the submission process. The process involves the checking of the metadata and the validating of the XAP file that you upload.
The assembly and data files must be packaged as an XAP file package. Visual Studio® 2010 Express for Windows Phone generates the necessary XAP package and manifest files.
|
Requirement |
Requirement Text |
|---|---|
|
4.1.1 - List of Package Requirements |
The maximum size of the XAP package file is 225 MB. The XAP package must contain the following:
|
|
4.1.2 - XAP File Repackaging Process |
When you submit the XAP file to Windows Phone Marketplace, the file is decompressed, validated, and repackaged. Repackaging involves the following steps:
|
|
Requirement |
Requirement Text |
|---|---|
|
4.2.1 |
You must develop your application using the documented APIs that are supported on the Windows Phone Application Platform for the OS version that your application is targeting. For more information, see the Class Library Reference for Windows Phone topic. For more information on new and changed APIs for Windows Phone OS 7.1, and information on application compatibility for the two Windows Phone OS versions, see the Windows Phone OS Application Compatibility section. |
|
4.2.2 |
The application must not invoke native code via PInvoke or COM interoperability. If it does, it will fail the certification process. |
|
4.2.3 |
The application must be compiled using retail configuration instead of debug. The application must not contain debugging symbols or output. |
|
4.2.4 |
The application must not redistribute the Windows Phone assemblies. However, you can re-distribute panorama, pivot, and map assemblies. |
|
4.2.5 |
The application must not call any APIs in the Microsoft.Xna.Framework.Game assembly or the Microsoft.Xna.Framework.Graphics assembly when using any methods from the System.Windows.Controls namespace. |
When you create a Windows Phone project using Visual Studio 2010 Express for Windows Phone, the Windows Phone application manifest file is auto-generated that includes a list of all the phone capabilities supported by Windows Phone. The phone capabilities listed on the application manifest file are displayed to the user during application purchase. In addition, operating system grants the security permissions to the application according to the capabilities listed on the manifest file. For more information, see the Application Manifest File for Windows Phone topic.
The application submission process uses Microsoft intermediate language (MSIL) code analysis to detect phone capabilities. The phone capabilities detected on your application are listed on the Windows Phone application manifest file replacing existing capabilities, as described in Step b, Section 4.1.2.
You can submit an application with obfuscated code and the detection process still applies.
The capability detection process does not discover Windows Phone APIs invoked via .NET reflection. As a result, the application will not have the security permissions required to run properly and will result in a failure during certification.
Microsoft recommends that you test the application with the same phone capabilities that are generated during the application submission process. To do this, you can run the Windows Phone Capability Detection tool and populate the application manifest file with the phone capabilities generated by the tool. After completing this step and building the application, if errors are reported, it might indicate that the application uses undocumented APIs or invokes APIs via .NET reflection. For more information, see the How to: Determine Application Capabilities topic.
Note:
|
|---|
|
The capability list can change across application updates. When you submit an application update for certification, it goes through the same process as the original application. |
Every application is targeted to publish to at least one specific geographic market and language. You can target multiple markets and submit your application in multiple languages. The language detection process includes the evaluation of the metadata that is used to describe the application and the UI text that is used within the application.
See Culture and Language Support for Windows Phone for a full list of supported languages in Windows Phone.
|
Requirement |
Requirement Text |
Test Steps |
|---|---|---|
|
4.4 Language Validation |
An application must be localized in at least one of the supported display languages for Windows Phone. For a full list of supported display languages, see Culture and Language Support for Windows Phone. A Windows Phone application will fail this requirement if a Neutral Language is not set. For more information on how to localize your application and how to set a Neutral Language, see How to: Build a Localized Application for Windows Phone. |
|
Requirement |
Requirement Text |
Test Steps |
|---|---|---|
|
4.5 Windows Phone Marketplace Iconography |
For each application, you must submit one icon to represent your application in the Windows Phone Marketplace catalog. This icon must match closely the icon provided in the XAP package. Users see this icon when browsing the application catalog on the phone before making a purchase. Caution:Do not use transparent PNG image files for the following phone application icons.
|
|
|
Requirement |
Requirement Text |
Test Steps |
|---|---|---|
|
4.6 Application Screenshot |
For each application, you must provide at least one or up to a maximum of eight screenshots. Users see these screenshots in the details page of the catalog before they make a purchase.
For more information, including how to use the built-in emulator screenshot tool, see How to: Create Screenshots for Windows Phone Marketplace. |
|
|
Requirement |
Requirement Text |
Test Steps |
|---|---|---|
|
4.7.1 Applicable Application Tile Images |
The large and small mobile app tile images must be representative of the application. |
|
Note:
Caution: