Windows 8编程入门：C#与XAML实战

4星 · 超过85%的资源需积分: 0 12 浏览量更新于2024-07-28 3 收藏 5.03MB PDF 举报

"Win8详解(C#&XMAL)" 是一本关于使用C#和XAML进行Windows 8应用开发的书籍，特别针对Windows RT平台。本书由Charles Petzold撰写，旨在帮助开发者在Windows 8 Consumer Preview阶段入门，解决当时Windows 8开发资料匮乏的问题。在Windows 8操作系统中，Windows Runtime (简称WinRT) 是一个新的核心API集，它是专门为现代应用程序设计的，支持C#、VB.NET、C++和JavaScript等多种编程语言。C#与XAML的组合成为构建Windows 8 Metro风格应用的主流选择，XAML（Extensible Application Markup Language）是一种用于定义用户界面的标记语言，它提供了声明式编程模型，让开发者能够轻松创建美观且响应式的UI。本书详细介绍了如何利用C#和XAML来编写Windows 8应用程序。内容可能包括以下几个方面： 1. **Windows 8开发环境**：设置Visual Studio IDE，配置开发环境，了解Metro风格应用的设计原则和用户体验指南。 2. **C#与WinRT交互**：讲解C#中的新特性，如async/await异步编程模型，以及如何调用WinRT API。 3. **XAML基础**：学习XAML语法，创建控件，理解数据绑定和模板，以及事件处理。 4. **UI布局**：探讨Grid、StackPanel、RelativePanel等布局容器的使用，实现响应式设计。 5. **导航和页面间通信**：掌握如何在不同页面间导航，以及如何在页面之间传递数据。 6. **资源和本地存储**：了解如何管理应用资源，以及如何使用IsolatedStorage进行本地数据存储。 7. **多媒体和图形**：利用XAML和C#处理图像、音频和视频，以及使用矢量图形和动画。 8. **后台任务和服务**：学习如何实现离线操作，后台任务，以及与云服务的集成。 9. **测试和调试**：介绍如何在模拟器和实际设备上调试应用，以及性能优化技巧。 10. **发布和应用生命周期**：指导如何打包和提交应用到Windows Store，以及理解应用的启动、暂停、恢复和终止等生命周期事件。本书不仅对初学者有很好的引导作用，还对有经验的开发者提供了深入理解WinRT平台和C# XAML开发的宝贵资源。尽管是基于Windows 8 Consumer Preview版本，其中的很多概念和原理在后续的Windows 8.1和Windows 10中依然适用，对于想要进入Windows应用开发领域的开发者来说，是一份宝贵的参考资料。

You can view either of these two files by double-clicking the file name or by right-clicking the file

name and choosing Open.

The BlankPage.xaml and BlankPage.xaml.cs files are linked in the Solution Explorer because they

both contribute to the definition of a class named BlankPage. For a simple program like Hello, this

BlankPage class defines all the visuals and user interface for the application. As the class name implies,

the visuals are initially "blank," but they won't be for long.

Despite its funny file name, BlankPage.xaml.cs definitely has a .cs extension, which stands for "C

Sharp." Stripped of all its comments, the skeleton BlankPage.xaml.cs file contains C# code that looks

like this:

using System;

using System.Collections.Generic;

using System.IO;

using System.Linq;

using Windows.Foundation;

using Windows.Foundation.Collections;

using Windows.UI.Xaml;

using Windows.UI.Xaml.Controls;

using Windows.UI.Xaml.Controls.Primitives;

using Windows.UI.Xaml.Data;

using Windows.UI.Xaml.Input;

using Windows.UI.Xaml.Media;

using Windows.UI.Xaml.Navigation;

namespace Hello

{

public sealed partial class BlankPage : Page

{

public BlankPage()

{

this.InitializeComponent();

}

protected override void OnNavigatedTo(NavigationEventArgs e)

{

}

The file is dominated by using directives for all the namespaces that you are anticipated to need.

You'll discover that most BlankPage.xaml.cs files don't require all these namespace names and many

others require some additional namespaces.

These namespaces fall into two general categories based on the first word in the name:

• System.* .NET for Metro style applications

• Windows.* Windows Runtime (or WinRT)

As suggested by the list of using directives, namespaces that begin with Windows.UI.Xaml play a major

role in the Windows Runtime.

Following the using directives, this BlankPage.xaml.cs file defines a namespace named Hello (the

same as the project name) and a class named BlankPage that derives from Page, a class that is part of

the Windows Runtime.

The documentation of the Windows 8 API is organized by namespace, so if you want to locate the

documentation of the Page class, knowing the namespace where it’s defined is useful. Let the mouse

pointer hover over the name Page in the BlankPage.xaml.cs source code, and you’ll discover that Page

is in the Windows.UI.Xaml.Controls namespace.

The constructor of the BlankPage class calls an InitializeComponent method (which I'll discuss

shortly), and the class also contains an override of a method named OnNavigatedTo. Metro style

applications often have a page-navigation structure somewhat like a website, and hence they often

consist of multiple classes that derive from Page. For navigational purposes, Page defines virtual

methods named OnNavigatingFrom, OnNavigatedFrom, and OnNavigatedTo. The override of

OnNavigatedTo is a convenient place to perform initialization when the page becomes active. But

that's for later; most of the programs in the early chapters of this book will have only one page. I’ll tend

to refer to an application’s “page” more than its “window.” There is still a window underneath the

application, but it doesn’t play nearly as large a role as the page.

Notice the partial keyword on the BlankPage class definition. This keyword usually means that the

class definition is continued in another C# source code file. In reality (as you’ll see), that’s exactly the

case. Conceptually, however, the missing part of the BlankPage class is not another C# code file but the

BlankPage.xaml file:

<Page

x:Class="Hello.BlankPage"

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

xmlns:local="using:Hello"

xmlns:d="http://schemas.microsoft.com/expression/blend/2008"

xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"

mc:Ignorable="d">

</Grid>

</Page>

This file consists of markup conforming to the standard known as the eXtensible Application Markup

Language, or XAML, pronounced “zammel.” As the name implies, XAML is based on eXtensible Markup

Language, or XML.

Generally, you'll use the XAML file for defining all the visual elements of the page, while the C# file

handles jobs that can't be performed in markup, such as number crunching and responding to user

input. The C# file is often referred to as the "code-behind" file for the corresponding XAML file.

The root element of this XAML file is Page, which you already know is a class in the Windows

Runtime. But notice the x:Class attribute:

<Page

x:Class="Hello.BlankPage"

The x:Class attribute can appear only on the root element in a XAML file. This particular x:Class

attribute translates as “a class BlankPage in the Hello namespace is defined as deriving from Page.” It

means the same thing as the class definition in the C# file!

The x:Class attribute is followed by a bunch of XML namespace declarations. As usual, these URIs

don’t actually reference interesting webpages but instead serve as unique identifiers maintained by

particular companies or organizations. The first two are the most important:

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

The 2006 date harkens back to Microsoft's introduction of the Windows Presentation Foundation

and the debut of XAML. WPF was part of the .NET Framework 3.0, which prior to its release was known

as WinFX, hence the “winfx” in the URI. To a certain extent, XAML files are compatible between WPF,

Silverlight, Windows Phone, and the Windows Runtime, but only if they use classes, properties, and

features common to all the environments.

The first namespace declaration with no prefix refers to public classes, structures, and enumerations

defined in the Windows Runtime, which includes all the controls and everything else that can appear in

a XAML file, including the Page and Grid classes in this particular file. The word "presentation" in this

URI refers to a visual user interface, and that distinguishes it from other types of applications that can

use XAML. For example, if you were using XAML for the Windows Workflow Foundation (WF), you'd

use a default namespace URI ending with the word "workflow".

The second namespace declaration associates an “x” prefix with elements and attributes that are

intrinsic to XAML itself. Only nine of these are applicable in Windows Runtime applications, and

obviously one of the most important is the x:Class attribute.

The third namespace declaration is interesting:

xmlns:local="using:Hello"

This associates an XML prefix of local with the Hello namespace of this particular application. You

might create custom classes in your application, and you'd use the local prefix to reference them in

XAML. If you need to reference classes in code libraries, you’ll define additional XML namespace

declarations that refer to the assembly name and namespace name of these libraries. You’ll see how to

do this in chapters ahead.

The remaining namespace declarations are for Microsoft Expression Blend. Expression Blend might

insert special markup of its own that should be ignored by the Visual Studio compiler, so that’s the

reason for the Ignorable attribute, which requires yet another namespace declaration. For any program

in this book, these last three lines of the Page root element can be deleted.

The Page element has a child element named Grid, which is another class defined in the

Windows.UI.Xaml.Controls namespace. The Grid will become extremely familiar. It is sometimes referred

to as a "container" because it can contain other visual objects, but it’s more formally classified as a

"panel" because it derives from the Panel class. Classes that derive from Panel play a very important

role in layout in Metro style applications. In the BlankPage.xaml file that Visual Studio creates for you,

the Grid is assigned a background color (actually a Brush object) based on a predefined identifier using

a syntax I'll discuss in Chapter 2, “XAML Syntax.”

Generally, you’ll divide a Grid into rows and columns to define individual cells (as I’ll demonstrate in

Chapter 5, “Control Interaction”), somewhat like a much improved version of an HTML table. A Grid

without rows and columns is sometimes called a "single-cell Grid" and is still quite useful.

To display up to a paragraph of text in the Windows Runtime, you’ll generally use a TextBlock

(another class defined in the Windows.UI.Xaml.Controls namespace), so let’s put a TextBlock in the

single-cell Grid and assign a bunch of attributes. These attributes are actually properties defined by the

TextBlock class:

Project: Hello | File: BlankPage.xaml (excerpt)

<TextBlock Text="Hello, Windows 8!"

FontFamily="Times New Roman"

FontSize="96"

FontStyle="Italic"

Foreground="Yellow"

HorizontalAlignment="Center"

VerticalAlignment="Center" />

</Grid>

Note In this book, whenever a block of code or markup is preceded by a heading like this one, you'll

find the code among this book's downloadable companion content. Generally I’ll just show an excerpt

of the total file, but with enough context so you know exactly where it is.

The order of these attributes doesn't matter, and of course the indentation doesn’t matter, and all

of them except the Text attribute can be skipped if you're in a hurry. As you type you'll notice that

Visual Studio's Intellisense feature suggests attribute names and possible values for you. Often you can

just select the one you want. As you finish typing the TextBlock, Visual Studio's design view gives you a

剩余293页未读，继续阅读

Trent1985

粉丝: 5383
资源: 72

Windows 8编程入门：C#与XAML实战

XAML.rar_XMAL_c# xmal编程_xaml_xaml代码包下载_xaml编程学习网

2048_2048_

Button.xmal

C#中WPF ListView绑定数据的实例详解

WPF XMAL 添加字体

WPF纯XMAL画图标

WPF XMAL一个WIN10启动界面圆圈动画

wpf xmal开发文档

xmal 获取当前时间

app.xmal 全局变量

最新资源