Charles Petzold的Windows编程第6版：C#与XAML编写Windows 8应用

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

"Programing Windows 6th - Charles Petzold 的《编写 Windows 8 应用程序使用 C# 和 XAML 消费者预览版电子书》" 本书是 Charles Petzold 的经典之作《Programming Windows》的第六版，特别关注了如何使用 C# 和 XAML 编写 Windows 8 应用程序。Petzold 是一位资深的程序员和技术作家，以其深入浅出的解释和技术洞察力在 IT 领域享有盛誉，尤其在 Windows 开发方面。《Programming Windows》系列自早期版本以来，一直是 Windows API 编程的重要参考资料，而第六版则适应了 Windows 8 平台的发展，聚焦于现代 UI（以前称为 Metro Style）应用程序的开发。C# 是微软推广的面向对象的编程语言，常用于构建 Windows 应用程序，而 XAML（可扩展应用程序标记语言）则是一种用于描述用户界面的 XML 基础标记语言，尤其适合创建数据绑定和动态更新的 UI。书中涵盖的知识点包括： 1. **Windows 8 平台概述**：介绍 Windows 8 的操作系统架构，以及它如何支持触控、键盘和鼠标交互，以及多设备兼容性。 2. **C# 语言基础**：讲解 C# 的基本语法、类、对象、接口、异常处理和集合等核心概念，为编写 Windows 应用程序打下基础。 3. **XAML 基础**：解释 XAML 的语法规则，如何定义用户界面元素、数据绑定和事件处理，以及如何使用样式和模板来实现界面一致性。 4. **Windows Runtime (WinRT)**：深入探讨 WinRT，这是 Windows 8 平台上应用程序编程接口的新框架，提供跨语言的互操作性。 5. **UI 设计与交互**：教授如何设计符合现代 UI 设计原则的界面，包括动态磁贴、平滑动画和触摸友好布局。 6. **应用生命周期管理**：详细讲解 Windows 8 应用的启动、暂停、恢复和关闭过程，以及后台任务和资源管理。 7. **数据存储和同步**：介绍本地存储选项，如应用数据容器、文件系统和SQLite数据库，以及云同步策略。 8. **网络编程**：讲解如何使用 HTTP 和其他协议进行网络通信，包括异步编程模型以确保应用响应性。 9. **多媒体和图形**：涵盖图像、音频和视频处理，以及利用 DirectX 进行高性能图形编程的方法。 10. **测试和调试**：提供测试策略和调试工具的使用指南，帮助开发者优化和验证代码。 11. **发布和市场策略**：介绍将应用程序提交到 Windows Store 的流程，以及如何制定有效的市场推广计划。本书不仅适合有经验的 Windows 开发者升级技能，也适合初学者入门，通过实例和详尽的解释，帮助读者掌握 Windows 8 应用程序开发的核心技术和实践方法。由于此书支持的是 Windows 8 Consumer Preview 版本，读者需要注意，随着 Windows 8 的后续版本发布，可能需要参考最新文档以获取最新的开发信息。

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

gnimgnot

粉丝: 753
资源: 27

Charles Petzold的Windows编程第6版：C#与XAML编写Windows 8应用

《Programing Windows 5th》

windows programing 5th

Programming Windows(5th)(中英文全）

Oasys是一个使用Maven进行项目管理的OA办公自动化系统。该项目基于Spring B

peewee-3.15.0-cp310-cp310-win_amd64.whl

Delphi 12控件之FR安装工具24.7z

基于树莓派使用sht20采集温湿度信息，以JSON格式上传至MQTT，MQTT发布开关灯指令，树莓派执行指令操作

数据可视化面板-ECharts.zip

机器人上下楼梯控制系统的设计与实现

nlopt-2.7.1-cp38-cp38-win_amd64.whl

最新资源