Charles Petzold的Windows编程第六版英文高清电子书

需积分: 0 46 浏览量更新于2024-07-26 收藏 5.03MB PDF 举报

"Windows编程（第六版）是Charles Petzold的经典著作，是一本关于Windows编程的权威指南，尤其适合作为程序员的案头参考书。本书不仅涵盖了传统的Windows编程技术，还与时俱进地讨论了如何使用C#和XAML编写Windows 8应用程序，适应现代操作系统的发展。" 本书第六版主要知识点包括： 1. **Windows编程基础**：介绍Windows编程的基本概念，如窗口、消息队列、消息循环和事件处理。这些基础知识是理解Windows应用程序运行机制的关键。 2. **API调用与系统交互**：讲解如何使用Windows API进行系统级别的交互，如内存管理、进程和线程控制，以及文件和网络操作。这将帮助开发者深入理解Windows操作系统的工作原理。 3. **图形设备接口GDI**：详细介绍如何使用GDI进行图形绘制，包括基本的几何形状、字体、位图操作等，以及高级的图形渲染技巧。 4. **用户界面设计**：探讨创建和管理窗口控件，如按钮、文本框、菜单和对话框，以及响应用户输入的策略。 5. **Windows事件模型**：解析Windows的消息传递系统，包括消息的发送、接收和处理，以及如何使用消息映射机制。 6. **C#和XAML**：针对Windows 8应用程序开发，讲解如何使用C#语言和XAML（Extensible Application Markup Language）来构建现代化的用户界面，包括XAML的语法、控件和布局系统。 7. **Windows Store应用开发**：详细介绍Windows Store应用的生命周期、沙箱环境、权限管理，以及如何发布和更新应用。 8. **调试和性能优化**：提供Windows应用程序的调试技巧，包括使用调试器和性能分析工具，以及如何提高代码的运行效率。 9. **实例解析**：书中包含大量实例代码，帮助读者理解和应用所学知识，这些实例涵盖各种复杂度，从简单的窗口程序到完整的应用示例。 10. **最新技术动态**：尽管是英文版，但本书考虑到了Windows操作系统的发展，对Windows 8及以后版本的支持，使得内容与时俱进。通过学习《Windows编程（第六版）》，读者不仅能掌握Windows编程的核心技能，还能了解到最新的开发趋势和技术，为成为专业的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页未读，继续阅读

ZammerLink

粉丝: 0
资源: 2

Charles Petzold的Windows编程第六版英文高清电子书

寒江独钓:Windows内核安全编程 高清 电子版文

Windows 网络编程2

Windows Shell扩展编程完全指南

Windows Shell扩展编程完全指南(含代码)

C#编程经典：Thinking in C#高清完整版指南

Visual C++ 2005 Windows编程指南

2025年软考高级 - 信息系统项目管理师考试备考全攻略

MySQL 5.7从入门到精通 第23章 新闻发布系统数据库设计 共6页.pptx

高分springboot毕设+vue的游戏创意工坊与推广平台的设计与实现_orv论文-Java源码.zip

考研助手--论文.zip

最新资源

寒江独钓:Windows内核安全编程高清电子版文

MySQL 5.7从入门到精通第23章新闻发布系统数据库设计共6页.pptx