C#与XAML开发Win8应用指南：Petzold深度解析

5星 · 超过95%的资源需积分: 50 77 浏览量更新于2024-07-25 收藏 22.79MB PDF 举报

《利用C#和XAML编写Win 8及WP8应用程序》是一本由微软于2013年发布的专业技术书籍，作者是Charles Petzold。本书针对Windows 8和Windows Phone 8（简称Win 8和WP8）平台，介绍了如何使用C#（一种广泛应用于.NET框架下的高级编程语言）和XAML（XML为基础的用户界面描述语言）来开发高效、现代的应用程序。WinRT（Windows Runtime）是Windows 8及之后版本的核心组件，它提供了跨设备和操作系统版本的开发一致性。书中详细阐述了Windows 8应用程序设计的基础，包括对C#语法和面向对象编程的深入解析，以及XAML在创建美观且响应式的用户界面中的关键作用。读者将学习到如何构建Windows Store应用商店（现称Microsoft Store）上的应用程序，以及如何处理与Windows 8特有功能如触摸输入、多任务处理、 metro风格界面和 Metro应用的集成。作者Charles Petzold以其丰富的经验和清晰的讲解，引导读者逐步掌握开发Windows 8应用所需的技能，无论是初学者还是经验丰富的开发者，都能从中获益。此外，书中还包含了大量的示例代码和实用技巧，帮助读者在实际项目中快速上手。版权方面，这本书受到严密保护，未经Microsoft Press许可，任何部分内容不得复制或传播。如果你在阅读过程中遇到问题，可以通过电子邮件联系Microsoft Press Book Support获取支持，同时，微软鼓励读者对书籍质量进行反馈，以持续改进。《利用C#和XAML编写Win 8及WP8应用程序》是一本深度覆盖Windows 8开发环境和技术的权威指南，对于希望通过C#和XAML技术在移动和桌面领域打造卓越应用的开发者来说，这是一本不可或缺的参考资料。

xvi Introduction

The new Windows Store applications represent a radical break with traditional

Windows. The programs generally run in a full-screen mode—although two programs

can share the screen in a “snap” mode—and many of these programs will probably be

optimized for touch and tablet use. These applications are purchasable and installable

only from the application store run by Microsoft. (As a developer, you can deploy and

test applications directly from Visual Studio.)

In addition to the versions of Windows 8 that run on x86 processors, there is also a

version of Windows 8 that runs on ARM processors, most commonly found in low-cost

tablets and other mobile devices. This version of Windows 8 is called Windows RT,

and it only comes preinstalled on these machines. One of the rst computers running

Windows RT is the initial release of the Microsoft Surface.

Aside from some preinstalled desktop applications, Windows RT runs new Windows

Store applications only. You cannot run existing Windows 7 applications under

Windows RT. You cannot run Visual Studio under Windows RT, and you cannot develop

Windows 8 applications under Windows RT.

The Windows 8 user interface incorporates a new design paradigm that is likely to

be reected in Windows Store applications. Somewhat inspired by signage in urban

environments, this design paradigm emphasizes content over program “chrome” and is

characterized by the use of unadorned fonts, clean open styling, a tile-based interface,

and transitional animations.

Many developers were rst introduced to the Windows 8 design paradigm with

Windows Phone 7, so it’s interesting to see how Microsoft’s thinking concerning large

and small computers has evolved. In years gone by, Microsoft attempted to adapt the

design of the traditional Windows desktop to smaller devices such as hand-held com-

puters and phones. Now a user-interface design for the phone is being moved up to

tablets and the desktop.

One important characteristic of this new environment is an emphasis on multitouch,

which has dramatically changed the relationship between human and computer. In

fact, the term “multitouch” is now outmoded because virtually all new touch devices

respond to multiple ngers. The simple word “touch” is now sufcient. Part of the

new programming interface for Windows 8 applications treats touch, mouse, and

pen input in a unied manner so that applications are automatically usable with all

three input devices.

Introduction xvii

The Focus of This Book

This book focuses exclusively on writing Windows Store applications. Plenty of other

books already exist for writing Win32 desktop applications, including the 5

edition

of Programming Windows

. I’ll occasionally make reference to Win32 API and desktop

applications, but this book is really all about writing new Windows 8 applications.

For writing these applications, a new object-oriented API has been introduced called

the Windows Runtime or WinRT (not to be confused with the version of Windows 8 that

runs on ARM processors, called Windows RT). Internally, the Windows Runtime is based

on COM (Component Object Model) with interfaces exposed through metadata les

with the extension .winmd located in the /Windows/System32/WinMetadata directory.

Externally, it is very object-oriented.

From the application programmer’s perspective, the Windows Runtime resembles

Silverlight, although internally it is not a managed API. For Silverlight programmers,

perhaps the most immediate difference involves namespace names: the Silverlight

namespaces beginning with System.Windows have been replaced with namespaces

beginning with Windows.UI.Xaml

Most Windows 8 applications will be built not only from code but also markup,

either the industry-standard HyperText Markup Language (HTML) or Microsoft’s

eXtensible Application Markup Language (XAML). One advantage of splitting an

application between code and markup is potentially splitting the development of the

application between programmers and designers.

Currently there are three main options for writing Windows 8 applications, each of

which involves a programming language and a markup language:

■

C++ with XAML

■

C# or Visual Basic with XAML

■

JavaScript with HTML5

The Windows Runtime is common to all these options, but the Windows Runtime is

also supplemented by another programming interface appropriate for the particular

language. Although you can’t mix languages within a single application, you can create

libraries (called Windows Runtime Components) with their own .winmd les that can be

accessed from any other Windows 8 language.

xviii Introduction

The C++ programmer uses a dialect of C++ called C++ with Component

Extensions, or C++/CX, that allows the language to make better use of WinRT. The C++

programmer also has direct access to a subset of the Win32 and COM APIs, as well as

DirectX. C++ programs are compiled to native machine code.

Programmers who use the managed languages C# or Visual Basic .NET will nd

WinRT to be very familiar territory. Windows 8 applications written in these languages

can’t access Win32, COM, or DirectX APIs with as much ease as the C++ programmer,

but it is possible to do so, and some sample programs in Chapter 15, “Going Native,”

show how. A stripped-down version of .NET is also available for performing low-level

tasks.

For JavaScript, the Windows Runtime is supplemented by a Windows Library for

JavaScript, or WinJS, which provides a number of system-level features for Windows 8

apps.

After much consideration (and some anguish), I decided that this book would focus

almost exclusively on the C# and XAML option. For at least a decade I have been con-

vinced of the advantages of managed languages for development and debugging, and

for me C# is the language that has the closest t to the Windows Runtime. I hope C++

programmers nd C# code easy enough to read to derive some benet from this book.

I also believe that a book focusing on one language option is more valuable than

one that tries for equal coverage among several languages. There will undoubtedly be

plenty of other Windows 8 books that show how to write Windows 8 applications using

the other options.

With that said, I have greatly enjoyed the renewed debate about the advantages of

C++ and native code in crafting high-performance applications. No single tool is best

for every problem, and I will be exploring C++ and DirectX development for Windows 8

more in the future, both in my blog and the pages of MSDN Magazine. As a modest

start, the companion content for this book includes all the program samples converted

to C++.

Introduction xix

The Approach

In writing this book, I’ve made a couple assumptions about you, the reader. I assume

that you are comfortable with C#. If not, you might want to supplement this book with

a C# tutorial. If you are coming to C# from a C or C++ background, my free online book

.NET Book Zero: What the C or C++ Programmer Needs to Know About C# and the .NET

Framework

might be adequate. This book is available in PDF or XPS format at

www.charlespetzold.com/dotnet

I also assume that you know the rudimentary syntax of XML (eXtensible Markup

Language) because XAML is based on XML. But I assume no familiarity with XAML or

any XAML-based programming interface.

This is an API book rather than a tools book. The only programming tool I use in this

book is Microsoft Visual Studio Express 2012 for Windows 8 (which I’ll generally simply

refer to as Visual Studio).

Markup languages are generally much more toolable than programming code.

Indeed, some programmers even believe that markup such as XAML should be entirely

machine-generated. Visual Studio has a built-in interactive XAML designer that

involves dragging controls to a page, and many programmers have come to know and

love Microsoft Expression Blend for generating complex XAML for their applications.

( Expression Blend is included among the free download of the development tools and

SDK I mentioned earlier.)

While such design tools are great for experienced programmers, I think that the

programmer new to the environment is better served by learning how to write XAML

by hand. That’s how I’ll approach XAML in this book. The XAML Cruncher tool featured

in Chapter 8, “App Bars and Popups,” is very much in keeping with this philosophy: it

lets you type in XAML and interactively see the objects that are generated, but it does

not try to write XAML for you.

On the other hand, some programmers become so skilled at working with XAML

that they forget how to create and initialize certain objects in code! I think both skills

are important, and consequently I often show how to do similar tasks in both code

and markup.

xx Introduction

As I began working on this book, I contemplated different approaches to how a

tutorial about the Windows Runtime can be structured. One approach is to start with

rather low-level graphics and user input, demonstrate how controls can be built, and

then describe the controls that have already been built for you.

I have instead chosen to focus initially on those skills I think are most important for

most mainstream programmers: assembling the predened controls in an application

and linking them with code and data. This is the focus of the 12 chapters of the book’s

Part I, “Elementals.” One of my goals in Part I is to make comprehensible all the code

and markup that Visual Studio generates in the various project templates it supports.

Part II, “Specialities,” covers more low-level and esoteric tasks, such as touch, bitmap

graphics, rich text, printing, and working with the orientation and GPS sensors.

Source Code

Learning a new API is similar to learning how to play basketball or the oboe: You don’t

get the full benet by watching someone else do it. Your own ngers must get involved.

The source code in these pages is downloadable via the “Companion Content” link here:

http://shop.oreilly.com/product/0790145369079.do

But you’ll learn better by actually typing in the code yourself.

My Setup

For writing this book, I used the special version of the Samsung 700T tablet that was

distributed to attendees of the Microsoft Build Conference in September 2011. (For

that reason, it’s sometimes called the Build Tablet.) This machine has an Intel Core i5

processor running at 1.6 GHz with 4 GB of RAM and a 64-GB hard drive. The screen

(from which most of the screenshots in the book were taken) has 8 touch points and a

resolution of 1366 × 768 pixels, which is the lowest resolution for which snap views are

supported.

Although the Build Tablets were originally distributed with the Windows 8 Developer

Preview installed, I progressively replaced that with the Consumer Preview (build 8250)

in March 2012 and the Release Preview (build 8400) in June 2012, and eventually the

ofcial release of Windows 8 Pro. Except when testing orientation sensors, I generally

used the tablet in the docking port with an external 1920×1080 HDMI monitor, and an

external keyboard and mouse.

剩余1135页未读，继续阅读

deepinnet

粉丝: 5
资源: 4

C#与XAML开发Win8应用指南：Petzold深度解析

Windows8应用程序揭秘，使用XAML和C＃编程语言

Windows 8 App Projects: XAML and C# Edition

Windows8高级编程：使用C#和XAML开发应用

c# with open

例子C#和axaml

Learn wpf mvvm-xaml,C# and the mvvm pattern

如何用c#编码实现xaml转html

c# 读取xaml 资源文件 demo

c# xaml安卓串口通讯

c#xaml中怎么连接串口

最新资源