Windows 8编程实战：C#与XAML开发指南（第六版）

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

《Windows®编程：第六版——使用C#和XAML编写Windows 8应用（消费者预览版电子书）》是由查尔斯·佩佐尔德所著，由微软出版社出版，是专为Windows 8编程爱好者和开发者设计的一本详尽指南。本书针对的是Windows 8 Consumer Preview时期的开发环境和技术，主要介绍了如何利用C#（一种强大的、面向对象的编程语言）和XAML（一种基于XML的语言，用于构建用户界面）来创建应用程序。书中涵盖了Windows 8平台的关键知识点，包括但不限于： 1. **Windows 8基础知识**：介绍Windows 8的特性和架构，特别是其与传统Windows版本的区别，如 Metro用户界面（Modern UI）的设计原则和特性。 2. **C#语言概论**：回顾C#的核心概念，如类、对象、继承、接口、多态性等，并重点讲解如何在Windows 8环境中高效地运用C#进行编程。 3. **XAML语言详解**：深入解析XAML的语法和设计模式，包括数据绑定、控件使用、布局管理、样式和模板等，帮助读者掌握如何创建美观且交互性强的UI组件。 4. **应用程序开发流程**：从项目设置、代码组织到调试和发布，全面介绍Windows Store应用程序开发的生命周期，以及如何适配不同设备和分辨率。 5. **Windows 8应用程序特有功能**：涵盖Windows 8特有的特性，如触摸操作优化、 charms bar（侧边栏）、Live Tiles（动态磁贴）和SkyDrive集成等。 6. **API和框架整合**：讲解如何与Windows 8的系统级API和库（如Windows.Storage、Windows.Networking等）无缝协作，实现更复杂的功能。 7. **安全和性能优化**：讨论如何确保应用程序的安全性和高效运行，包括处理敏感数据、内存管理和性能瓶颈的识别与解决。 8. **实战项目和案例分析**：书中还包含一系列实际项目的指导和示例，以便读者通过实践加深理解和技能提升。值得注意的是，由于本书针对的是消费者预览版，因此其中的一些技术和细节可能会随着Windows 8最终版的发布而有所变化。然而，作为一份基础资源，它依然能提供早期Windows 8开发的核心原理和技巧，对今天的开发者仍然具有参考价值，特别是在Windows Store应用开发的初期阶段。

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页未读，继续阅读

hejian1106

粉丝: 1
资源: 10

Windows 8编程实战：C#与XAML开发指南（第六版）

Essbase.py：Python通过MaxL模块访问Oracle Essbase数据库

TPS5430与MAXl674构建的智能太阳能充电器

编程规范：变量与命名约定详解

模拟技术中的高速\多通道8位ADC-MAXl55/6原理及在雷达应用

Ruby/MaxL-开源

基于MAXl660的镍氢电池充放电电路

essbasepy:MaxL Python 模块 Essbase.py-开源

MAXl01A在1GHz数字射频存储器的的应用

基于MAXQ3212和MAXl473的汽车无线遥控开门系统设计方案

最新资源