How to create a basic package manifest for Windows 8

Note  For Windows 10, see What's different in Windows 10.

 

To package your app, you must create a package manifest that contains the elements that are required by that the package manifest schema.

Alternatively, you can package your app using Visual Studio. See Packaging your app using Visual Studio.

Instructions

Step 1: Create the .appxmanifest File

Using a text editor, create a file (which will contain XML) and name it Package.appxmanifest.

Step 2: Add the basic template

Add this template to your Package.appxmanifest file.

<?xml version="1.0" encoding="utf-8"?>
<Package xmlns="http://schemas.microsoft.com/appx/2010/manifest">
  <Identity Name="" 
            Version="" 
            Publisher="" />
  <Properties>
    <DisplayName></DisplayName>
    <PublisherDisplayName></PublisherDisplayName>
    <Logo></Logo>
  </Properties>
  <Prerequisites>
    <OSMinVersion></OSMinVersion>
    <OSMaxVersionTested></OSMaxVersionTested>
  </Prerequisites>
  <Resources>
    <Resource Language="" />
  </Resources>
  <Applications>
    <Application Id="" StartPage="">
      <VisualElements DisplayName="" Description=""
           Logo="" SmallLogo=""  
           ForegroundText="" BackgroundColor="">
         <SplashScreen Image="" />
      </VisualElements>
    </Application>
  </Applications>
</Package>

The next steps show you how to fill in the elements and attributes that are required to complete the template.

Step 3: Add the identity info

The Identity element has 3 required attributes. Here's an example Identity element with placeholder text for the attributes. The values of the Name attribute and the Publisher attribute (the values of CN, O, L, S, and C) in the example below are provided by the store, for apps which are uploaded to the store.

<Identity Name="MyCompany.MySuite.MyApp" 
          Version="1.0.0.0" 
          Publisher="CN=MyCompany, O=MyCompany, L=MyCity, S=MyState, C=MyCountry"/>

Step 4: Add the package properties

The Properties element has 3 required child elements. Here is an example Properties node with placeholder text for the elements. The DisplayName is the name of your app that you reserve in the store, for apps which are uploaded to the store.

<Properties>
  <DisplayName>MyApp</DisplayName>
  <PublisherDisplayName>MyCompany</PublisherDisplayName>
  <Logo>images\icon.png</Logo>
</Properties>

Step 5: Add the prerequisites

Here is an example Prerequisites node.

<Prerequisites>
  <OSMinVersion>6.2.1</OSMinVersion>
  <OSMaxVersionTested>6.2.1</OSMaxVersionTested>
</Prerequisites>

Step 6: Add the resources

Here is an example Resources node.

<Resources>
  <Resource Language="en-us" />
</Resources>

Step 7: Add the optional info

You can use the Applications element to specify one or more apps for the package. Note that although each package can contain one or more apps, packages that contain multiple apps won't pass the Microsoft Store certification process.

The entry for an app must specify certain attributes of the VisualElements element and a SplashScreen element. This entry can also specify a DefaultTile element. Here is an example Applications node with placeholder text.

<Applications>
  <Application Id="MyApp" StartPage="default.html">
    <VisualElements DisplayName="My App" Description="A useful description." 
         Logo="images\icon.png" SmallLogo="images\small_icon.png" 
         ForegroundText="dark" BackgroundColor="#FFFFFF" >
      <SplashScreen Image="images\splash.png" />
    </VisualElements>
  </Application>
</Applications>

How to create a package manifest manually