Discussion on Windows Phone 7 development on the 31st day -- 1st: Project template

By Jeff Blankenburg

Before writing"Discussion on Windows Phone 7 development on the 31st day"In the first article, we need to make some assumptions.

First, I suppose you know some Silverlight knowledge. Last year I wrote a series of articles about Silverlight on the 31st, so I suggest you start learning from Silverlight if you have never touched it. All the articles in this series assume that you have basic Silverlight knowledge.

Secondly, I suppose you have installed all the required tools. Here you can find and download them in http://developer.windowsphone.com. You need Visual Studio 2010 for Windows Phone and Expression Blend 4 for Windows Phone. You will certainly use these two, and they are completely free of charge. If you already have an official version of the software, it will update the templates of these projects rather than add new software on your machine.

Okay. Let's get started.

Today, let's look at a default Windows Phone Project template that comes with Visual Studio 2010:Windows Phone Application.

Solution Explorer(Solution Manager)

Let's take a look at the solution manager of the default project. I am not going to explain all the content of each file, but I will introduce their functions. If you want to read the content, install these tools! Very simple!

(At the end of the article, I provide project files for download .)

ApplicationIcon.png

You can use another image to represent the image of your program. The user will see this image in their program. It is very important and must be well designed.

App. xaml

This file is similar to the web. config file in ASP. NET. You can save the data and settings for the entire application. I also like to store my style data in this file, but this is not necessary.

App. xaml. cs

The "post-code" file of the above file, where you can process the "Tombstone" of the program ". We will explain the concept of multi-task and tombstone in 14th days.

AppManifest. xml

Generate a simple application list file required by the application installation package (XAP.

AssemblyInfo. cs

Another configuration file, which contains the name and version metadata, is embedded into the generated Assembly file.

Background.png

This image is displayed when your program is displayed on the Start interface. It should be like applicationicon.png.

MainPage. xaml

Your first program page. In almost every project, it should not be the only page. The phone can also process the front and back navigation between pages, so you should not pile up all the functions into a XAML page. Separate them and you will thank me later. We will explore the navigation between pages in tomorrow's article.

MainPage. xaml. cs

The "post-code" file on the home page. When you need to control some behaviors in the code, it is usually done here. Interaction with objects in a XAML file is almost essential. In this series of articles, there will be a lot of topics about writing code in this file (or other post-XAML code files.

SplashScreenImage.jpg

This image is displayed by default if your application takes a long time to load. You can replace the image by yourself, but remember that this only lets users know that they are waiting for the real application to load.

WMAppManifest. xml

Another metadata file that contains the specific data of the application, including the title, icon location, and functions.

Download sample code:

As I mentioned earlier, we will talk about inter-page navigation tomorrow. Goodbye!

Address: http://www.jeffblankenburg.com/post/31-Days-of-Windows-Phone-7c-Day-1-Project-Template.aspx