Skip to content

Latest commit

 

History

History
109 lines (64 loc) · 5.16 KB

submit-a-multiple-locale-device-manifest-package.md

File metadata and controls

109 lines (64 loc) · 5.16 KB
Raw
title description ms.topic ms.date
Submit a Multiple-locale device manifest package
Submit a Multiple-locale device manifest package
article
04/20/2017

Submit a Multiple-locale device manifest package

Submitting a multiple-locale device manifest package

You can use the same method to submit packages for preview or release.

To submit a device manifest package

  1. Sign the devicemanifest-ms package with the SignTool tool.

  2. Sign in to the Dashboard from either the Hardware Dev Center or the Windows Dev Center by using a Microsoft account.

  3. Under Device metadata, click Create experience if you want to submit a new experience, or click Manage experience if you want to modify an existing experience.

  4. Browse for and select your new devicemanifest-ms package, and then click Submit.

Creating a Device Manifest Submission Package

A device manifest submission package is the package format in which all multi-locale device metadata must be submitted to the Partner Center.

The device manifest submission package contains a file that declares locale support. The device manifest package also includes a device metadata package.

Device manifest submission packages can be uploaded to the Partner Center in the same way as device metadata packages. Using the same user interface and upload boxes, you enter the name of your *.devicemanifest-ms file for upload.

All file upload boxes other than bulk upload on the Dashboard’s user interface will accept device manifest submission packages.

Device Manifest Submission Package Contents

Each device manifest submission package consists of the following components:

  • Device metadata package

    This package contains information and graphics to display device icons, set actions, and utilize device experience features in Windows.

    The device metadata package is always required.

  • LocaleInfo XML document

    This document contains data about the locales included in the accompanying device metadata package. The Hardware Dev Center uses this data to properly validate the device metadata package for one or more locales.

    The LocaleInfo XML document is always required, even if the device metadata package only contains a single locale.

Structure of a Device Manifest Submission Package

The structure of a device manifest package depends on whether the included device metadata is for a PC, for mobile broadband, or contains support for multiple locales.

If the device metadata does not fall into any of the three categories, a device manifest package is not necessary. However, a device manifest package can still be used to indicate the device metadata package is for a single locale.

Structure of Multi-locale Device Manifest Submission Packages

If your device metadata package contains information for supporting multiple locales, it must still be submitted in a device manifest package.

The components of a device manifest submission package are stored in a compressed cabinet file. The file name must have a suffix of .devicemanifest-ms.

Each device manifest submission package must have the following structure:

GUID1.devicemanifest-ms
\GUID1.devicemetadata-ms
\LocaleInfo.xml

“GUID1” must be a GUID.

Instructions on creating LocaleInfo.xml are below.

To learn how to develop the device metadata package, *.devicemetadata-ms, see Device Metadata Package Schema Reference for Windows 8.

You can use the Cabarc tool to create these CAB packages. For more information about this tool, see Cabarc overview.

When you create a *.devicemanifest-ms file by using the Cabarc tool, you must create a local directory in which the device metadata package (*.devicemetadata-ms) and the LocaleInfo XML document are at the root of the directory.

Remarks

  • The .devicemanifest -ms and .devicemetadata-ms filenames must specify the GUID without the curly brace ({}) delimiters.

  • The GUID for each device manifest submission and device metadata package must be unique. When you create a new or revised package, you must create a new GUID.

  • For more details about how to create cabinet files, see the Microsoft Cabinet Software Development Kit.

Example

The following is an example of how to use the Cabarc tool to create a .devicemanifest-ms file. In this example, the components of the device manifest file are located in a local directory that is named DeviceManifestPackages:

.\DeviceManifestPackages\
.\DeviceManifestPackages\LocaleInfo.xml
.\DeviceManifestPackages\GUID.devicemetadata-ms

The GUID.devicemanifest-ms file was created in a local directory that is named ManifestFiles:

Cabarc.exe -r -p -P  .\DeviceManifestPackages\
N .\ManifestFiles\ GUID.devicemanifest-ms
.\DeviceManifestPackages\LocaleInfo.xml
.\DeviceManifestPackages\GUID.devicemetadata-ms

Creating LocaleInfo.xml

For information about creating the Localeinfo.xml file for submission, see Create the LocaleInfo.xml Submission File.