Join Doug Winnie for an in-depth discussion in this video Configuring the application manifest, part of Up and Running with Windows Phone 8 Development.
Before we can package and submit our app, there are few things we need to complete in the application manifest within Visual Studio. If you're a member, the Application Manifest is where we added our application icons to the app. We didn't look at the other tabs, but we'll do that in this video, and define some of the unique parameters that you'll need to work with in your own apps before you send them to Microsoft. If you still have the project open from the previous chapter, you can keep working with it. If not, open the project from the downloaded Exercise Files. Since we need to work with the AppManifest file, expand the Properties folder in the Solution Explorer, and double-click on WMAppManifest.xml.
Here we can see the app icons that we attached to our project in the previous chapter. One other field we should populate is the application description; just provide a simple description in here about what our app does. As a general hint, you may find it helpful to keep app descriptions and other descriptive text in a Word document, or in some other separate file. It makes it easier to update them as you add new versions, and keep them consistent if you're using them in multiple places. In addition, not all areas where you enter descriptions will have spell-checking support. Next, we need to define the capabilities of the application.
When you submit your app, you need to define all the hardware and network capabilities of the device. This is used to notify the user before they purchase or use the app that the app requires specific capabilities on the device. For instance, it may require access to the Internet, access to media services, access to your user account, file access, or other capabilities. Some users that are sensitive to access to their hardware, may not permit the use of these certain capabilities. It also provides extra security by notifying what an application can do. If you build an app, and not specifically request access to a capability, and then try to access it, the app will be denied that access.
In fact, an app may not successfully compile if you violate your defined capabilities rule, or it could be rejected during the app review cycle. Since our app doesn't require access to any unique hardware, we can uncheck all of the capabilities. The Requirements tab continues the list of allowable services that your app can work with. In this case, it is focused on hardware capabilities like cameras, near field communications, the compass, and motion sensors. Again, since our app doesn't require any of these, we can leave them unchecked. Finally, we have the Packaging tab. When we create our app and build the package or zap file, within it is metadata about the author, version number, and other information of the app.
Some of the information on this tab is automatically generated. So, unless you have a specific reason to do so, keep the Product ID and Publisher ID unchanged. These are the unique identifiers for your Application and Developer account that will link everything together in the distribution and reporting system at Microsoft. Let's go ahead and finish the rest of the information on this page. I'll put in my name as the Author. Publisher, I'll also make me. Since this is the first version of the app, we'll leave it at 1. 0.0.0. And, this is the unique Product ID that's been assigned to my app, as well as my personal Publisher ID.
Below, also are the default languages for the app. In this case, United States English, as well as other supported languages that the app can work with. With this tab finished, we are ready to build our release version, and begin the submission process. We'll do that in the next movie.
- Installing Visual Studio for Windows Phone
- Exploring the evolution of Windows Phone
- Laying out interface components with the StackPanel
- Adding buttons and text inputs
- Changing fonts and colors
- Building the application logic
- Testing in the simulator
- Adding design assets
- Deploying to the Windows Store