Charles Petzold教你利用C#和XAML开发Win8预览版应用

需积分: 10 171 浏览量更新于2024-07-27 收藏 9.26MB PDF 举报

《Windows®编程第六版：使用C#和XAML编写Win8应用》是Charles Petzold所著的一本面向Windows 8应用程序开发的指南，特别强调了使用C#（一种由微软公司开发的面向对象的编程语言）和XAML（一种基于XML的语言，用于构建用户界面）的技术。该书在2012年发布，正值Windows 8操作系统预览阶段，书中内容反映了当时的最新技术趋势。这本书对于想要尽早掌握Windows 8应用开发的读者来说是一份宝贵的资源，它详细讲解了如何利用C#的强大功能和XAML的直观设计来构建现代化的应用程序，这些应用能够充分利用Windows 8平台的特性和用户体验设计。Windows 8以其全新的 Metro UI设计风格和触控优化特性而备受瞩目，这使得本书的内容具有很高的实用价值。在学习过程中，读者可以了解到如何创建Windows Store应用，这是Windows 8的核心组成部分，这类应用可以在Windows Store中分发，并且能够运行在Windows 8的平板电脑、台式机以及智能手机等不同设备上。作者Charles Petzold以其深入浅出的讲解风格，带领读者一步步构建功能完整的应用程序，包括界面设计、事件处理、数据管理、网络通信等方面的知识。值得注意的是，由于这本书基于的是Windows 8的Release Preview版本，所以在实际操作中，某些技术和API可能会有所变化。然而，它提供的基础原理和设计理念对于后续的Windows开发仍然是有价值的。此外，书中还可能包含了一些关于版权和使用许可的重要信息，提醒读者在使用或传播书中的内容时必须遵循出版商的授权规定。《Windows®编程第六版：使用C#和XAML编写Win8应用》不仅是一本技术指南，也是一份历史记录，记录了Windows 8初期的开发环境和技术风貌，对那些对移动开发、跨平台应用和现代UI设计感兴趣的开发者来说，具有很高的参考价值。

getting close to the metal involved coding in assembly language, writing character output directly into

video display memory, and resorting to MS-DOS only for file I/O. In contrast, programming for

Windows involved a high-level language, completely unaccelerated graphics, and accessing hardware

only through a heavy layer of APIs and device drivers.

This switch from MS-DOS to Windows represented a deliberate forfeit of speed and efficiency in

return for other advantages. But what advantages? Many veteran programmers just couldn't see the

point. Graphics? Pictures? Color? Fancy fonts? A mouse? That’s not what computers are all about! The

skeptics called it the WIMP (window-icon-menu-pointer) interface, which was not exactly a subtle

implication about the people who chose to use such an environment or code for it.

Wait long enough, and a high-level language becomes a low-level language and multiple layers of

interface seemingly shrink down (at least in lingo) to a native API. Some C and C++ programmers of

today reject a managed language like C# on grounds of efficiency, and Windows has even sparked

some energetic controversy once again. Windows 8 is easily the most revolutionary updating to

Windows since its very first release in 1985, but many old-time Windows users are wondering about

the wisdom of bringing a touch-based interface tailored for smartphones and tablets to the

mainstream desktop.

I suppose that Programming Windows could only be persuaded to emerge from semi-retirement

with an exciting and controversial new user interface on Windows, and an API and programming

language suited to its modern aspirations.

Behind the Scenes

This book exists only because Ben Ryan and Devon Musgrave at Microsoft Press developed an

interesting way to release early content to the developer community and get advance sales of the final

book simultaneously. We are all quite eager to see the results of this experiment.

Part of the job duties of Devon and my technical reviewer Marc Young is to protect me from

embarrassment by identifying blunders in my prose and code, and I thank them both for finding quite

a few. Thanks also to Andrew Whitechapel for giving me feedback on the C++ sample code, and Brent

Rector for an email with a crucial solution for an issue involving touch. The errors that remain in these

chapters are my own fault, of course. I’ll try to identify the worst ones on my website at

www.charlespetzold.com/pw6. And also give me feedback about pacing and the order that I cover

material in these early chapters with an email to cp@charlespetzold.com.

Finally, I want to thank my wife Deirdre Sinnott for love and support and the necessary adjustments

to our lives that writing a book inevitably entails.

Charles Petzold

New York City and Roscoe, New York

Chapter 1

Markup and Code

Ever since the publication of Brian Kernighan and Dennis Ritchie's classic book The C Programming

Language (Prentice Hall, 1978), it has been customary for programming tutorials to begin with a simple

program that displays a short text string such as “hello, world.” Let’s create a few similar programs for

the new world of Windows 8.

I’ll assume you have the Windows 8 Release Preview installed with the development tools and

software development kit, specifically Microsoft Visual Studio Express 2012 RC for Windows 8, which

hereafter I’ll simply refer to as Visual Studio.

Launch Visual Studio from the Windows 8 start screen, and let's get coding.

The First Project

On the opening screen in Visual Studio, the Get Started tab should already be selected. Over at the left

you'll see a New Project option. Click that item, or select New Project from the File menu.

When the New Project dialog box comes up, select Templates in the left panel, then Visual C#, and

the option for creating a new Windows 8 project. From the list of available templates in the central

area, select Blank App (or the equivalent). Towards the bottom of the dialog box, type a project name

in the Name field: Hello, for example. Let the Solution Name be the same. Use the Browse button to

select a directory location for this program, and click OK. (I’ll generally use mouse terminology such as

“click” when referring to Visual Studio, but I’ll switch to touch terminology such as “tap” for the

applications you’ll be creating. A version of Visual Studio that is optimized for touch is probably at least

a few years away.)

Visual Studio creates a solution named Hello and a project within that solution named Hello, as well

as a bunch of files in the Hello project. These files are listed in the Solution Explorer on the far right of

the Visual Studio screen. Every Visual Studio solution has at least one project, but a solution might

contain additional application projects and library projects.

The list of files for this project includes one called MainPage.xaml, and if you click the little

arrowhead next to that file, you’ll see a file named MainPage.xaml.cs indented underneath

MainPage.xaml:

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

You'll discover that most MainPage.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 new Windows 8 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 MainPage.xaml.cs file defines a namespace named Hello (the

same as the project name) and a class named MainPage 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 MainPage.xaml.cs source code, and you’ll discover that Page

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

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

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

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 MainPage 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 MainPage class is not another C# code file but the

MainPage.xaml file:

<Page

x:Class="Hello.MainPage"

IsTabStop="false"

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">

剩余578页未读，继续阅读

celalnsa

粉丝: 0
资源: 5

Charles Petzold教你利用C#和XAML开发Win8预览版应用

CISSP McGraw.Hill.CISSP.Certification.All.in.One.Exam.Guide.4th.Edition.Nov.2007.pdf Part1

McGraw.Hill.CISSP.Certification.All.in.One.Exam.Guide.4th.Edition.Nov.2007.pdf

IBM.Press.DB2.9.for.Linux.UNIX.and.Windows.DBA.Guide.Reference.and.Exam.Prep6th.Edition.Nov.2007

manning.spring.in.action.4th.edition

hadoop.the.definitive.guide.4th.edition.1491901632

lectronic warfare and radar systems engineering handbook. 4th edition.

多元回归模型的参考文献

vector calculus, 6th edition by j.e. marsden and a. j. tromba, published by

Linux服务搭建参考文献

最新资源