Charles Petzold的《Windows编程》第六版解析Windows 8 App开发

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

"《Windows编程(第6版)》是由Charles Petzold编写的关于Windows应用程序开发的专业书籍，尤其关注使用C#和XAML编写Windows 8应用的 Consumer Preview版电子书。本书由Microsoft Press出版，是微软公司的一个部门发行。书中详细探讨了Windows编程的各种技术和实践，旨在帮助开发者理解Windows操作系统的核心机制，并利用这些知识创建现代应用程序。" 在Windows编程领域，Charles Petzold是一位备受尊敬的作者，他的书籍被广泛视为经典教程。《Windows编程(第6版)》不仅覆盖了传统的Windows API编程，还特别关注了针对Windows 8平台的应用程序开发，这其中包括使用C#这种面向对象的编程语言以及XAML（Extensible Application Markup Language）来构建用户界面。 C#是一种由微软开发的强大而现代的编程语言，特别适合Windows应用程序开发。它提供了面向对象的特性，如类、接口、继承和多态性，同时也支持函数式编程和泛型。在Windows 8中，C#与XAML的结合使得开发者能够更高效地构建具有丰富用户体验的UI。 XAML是一种声明式的标记语言，主要用于定义WPF（Windows Presentation Foundation）和UWP（Universal Windows Platform）应用的用户界面。通过XAML，开发者可以将UI设计与代码逻辑分离，从而实现更清晰的代码结构和更高的可维护性。XAML允许定义控件、布局、样式和数据绑定等元素，使得UI设计变得更加直观和灵活。本书会深入讲解Windows编程的核心概念，如消息循环、窗口过程、线程管理、内存管理和文件操作等。此外，还会介绍如何利用Windows 8特有的功能，如Live Tiles、Charms栏和触控支持等。开发者将学习到如何处理设备输入、存储和同步数据、集成云服务以及实现多设备兼容性。书中可能还涵盖了调试技术、性能优化和软件测试等方面，这些都是开发高质量Windows应用不可或缺的知识。尽管内容基于初步的软件版本，但Charles Petzold的作品通常会随着技术的发展而更新，以确保读者能够掌握最新的开发实践。需要注意的是，由于书中内容基于预发布版本，某些信息可能会在最终商业版本发布时发生变化。因此，读者在开发实际产品时应参考最新文档和API参考。尽管如此，这本书仍是一份宝贵的资源，可以帮助开发者掌握Windows编程的基础和高级技巧，从而在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页未读，继续阅读

bomberxjl

粉丝: 0
资源: 1

Charles Petzold的《Windows编程》第六版解析Windows 8 App开发

[电子书] Windows 编程 第6版 (英文版)

[Windows程序设计].Programming.Windows.EN.[Charles.Petzold]

《windows 程序设计》(Charles Petzold) 电子版 .CHM

programming windows英文第五版

Programming Windows

Windows程序设计(第五版).pdf

Programming Windows, Fifth Edition Code

Windows程序设计 (第五版) (C语言API) chm版word版

《编程Windows》第五版 - Charles Petzold著

Programming Windows 5E: Charles Petzold's Classic Guide

最新资源

[电子书] Windows 编程第6版 (英文版)