"Discover windows phone" 01. Project Template

“Discover Windows Phone” development series

Yasmine Abdelhady

@yasabdelhady

Yasmine.Abdelhady@Hotmail.com

01. Project Templates

© Yasmine Abdelhady| MEA DPE Intern

Agenda

Create New Blank App

Designer vs XAML pane

Solution Explorer components

© Yasmine Abdelhady| MEA DPE Intern

Create New Blank App

Windows Phone Application:1. Open Visual Studio 20132. File> New Project3. Under Visual C#>Choose Windows Phone> Windows Phone Application

© Yasmine Abdelhady| MEA DPE Intern

© Yasmine Abdelhady| MEA DPE Intern

Designer Pane XAML Pane

Solution Explorer

Lets take a look at the Solution Explorer for a default project and see what does it contain and the purpose of each.

Solution Explorer Components

AppManifest.xmlA simple application manifest file that is required to generate the application package (XAP) for store submission.

Solution Explorer Components

AssemblyInfo.csAnother configuration file that contains the name and version metadata ,including the copyrights, that is embedded into the generated assembly file.

Solution Explorer Components

WMAppManifest.xmlAnother metadata field that contains application specific data that are categorized into four parts1. Application UI; Display Name, description, app icon, first page to navigate to, etc.2. Capabilities; this is where you tell the device that you will use capabilities like accessing user's contacts or using location services, etc.3. Requirements; This part is where you specify some hardware requirements needed to run the application, like NFC.4. Packaging; this is where to specify some data about the packaging file, like author, version, publisher, etc.

Solution Explorer Components

ApplicationIcon.pngReplace this image with the one you want to represent your application on the phone.  This is what the users will see when they see your application on their phone.  Make it count.

Solution Explorer Components

AppResources.resxFor localizing the applicartion, basically you need to separate localizable resources from the rest of the code by creating language-specific resource files. Visual Studio uses these files to create assemblies that allow your application to support many languages.

Solution Explorer Components

App.xamlIt is where you keep universal data and settings for your entire application.  You can also keep my style data in this file as well, but it’s not required to do so.

Solution Explorer Components

App.xaml.csThe code-behind for App.xaml (any .xaml file has a .cs file for the code behind), this is where you will handle the back-end of your application.  

Solution Explorer Components

MainPage.xamlYour first application page (unless you change it in WMAppManifest.xml). Don't make it the only page in the application. The phone handles forward and backward navigation very well, and you should not bury all of your application's functionalities on one xaml file.

Solution Explorer Components

MainPage.xaml.csThe code-behind for the MainPage.xaml file.  When you need to make things happen in code, this is where you’ll generally write it.  Interacting with the objects on the XAML file is almost always a necessity.

Thank you

@yasabdelhady

yasmine.Abdelhady@Hotmail.com

yasabdelhady.wordpress.com

Facebook.com/yasabdelhady