Part A: Using the knowledge gained from create a PHONE app (It must be shown as
ID: 3822558 • Letter: P
Question
Part A: Using the knowledge gained from create a PHONE app (It must be shown as working in one of the phone emulators) that displays THREE paragraphs from your favorite book. You MUST use XAML code (instead of C# code) to format (set at least three properties for each paragraph... total of nine properties) and display the paragraphs, Turn in: 1. All XAML code you created. 2. At least two screen shots. One showing the XAML code within your editor. The other showing the results of the code in a phone emulator
Explanation / Answer
App.xaml is where you declare resources that are used across the app.
App.xaml.cs is the code-behind file for App.xaml. Like all code-behind pages, it contains a constructor that calls the InitializeComponent method. You don't write the InitializeComponent method. It's generated by Visual Studio, and its main purpose is to initialize the elements declared in the XAML file.
App.xaml.cs is the entry point for your app.
App.xaml.cs also contains methods to handle activation and suspension of the app.
MainPage.xaml
MainPage.xaml is where you define the UI for your app. You can add elements directly using XAML markup, or you can use the design tools provided by Visual Studio.
MainPage.xaml.cs is the code-behind page for MainPage.xaml. It's where you add your app logic and event handlers.
Together these two files define a new class called MainPage, which inherits from Page, in the HelloWorldnamespace.
Package.appxmanifest
A manifest file that describes your app: its name, description, tile, start page, etc.
Includes a list of the files that your app contains.
A set of logo images
Assets/Square150x150Logo.scale-200.png represents your app in the start menu.
Assets/StoreLogo.png represents your app in the Windows Store.
Assets/SplashScreen.scale-200.png is the splash screen that appears when your app starts.