UWP编程全方位指南

4星 · 超过85%的资源需积分: 33 79 浏览量更新于2024-07-19 3 收藏 65.17MB PDF 举报

"UWP编程宝典是一本全面且权威的指南，专注于介绍如何进行Universal Windows Platform（UWP）应用的开发。这本书以丰富的图文并茂形式呈现，内容通俗易懂，适合初学者和有一定经验的开发者。" 在深入探讨UWP编程之前，首先需要了解什么是UWP应用。UWP（Universal Windows Platform）是微软推出的跨平台应用开发框架，允许开发者编写一次代码，即可在所有支持Windows 10的设备上运行，包括PC、平板、手机、Xbox、HoloLens等。UWP旨在提供统一的用户体验，并简化开发流程。开始UWP开发之旅，你需要设置开发环境。确保你的设备已启用开发模式，这通常需要在设备设置中进行配置。接着，注册成为开发者，以便可以使用Visual Studio等工具创建和发布应用。对于初学者，创建你的第一个"Hello, world"应用是很好的起点，书中提供了使用C#、JavaScript和C++三种语言的教程。在UWP应用中支持触控和新型输入设备，如Surface Dial，是提升用户体验的关键。书中的章节指导你如何在应用中集成这些功能。此外，你可以学习如何构建WebVR游戏，利用Babylon.js库，将虚拟现实体验融入到UWP游戏中。规划应用设计和用户界面（UI）同样重要。UWP应用的设计原则包括直观的UI设计、布局、导航、命令、内容展示以及对不同屏幕尺寸的适应。书中介绍了如何使用XAML定义页面布局，使用各种布局面板如Grid和StackPanel创建复杂的界面结构。同时，你将学习到关于颜色、图标、动画、声音、字体等方面的风格设定，以及如何利用Acrylic、Reveal、Parallax等效果提升视觉质量。 UWP提供了一系列的控件和设计模式，帮助开发者实现常见的功能。比如AppBar和CommandBar用于实现顶部操作，Auto-suggestBox用于智能提示，Buttons处理用户交互，Checkbox用于选项选择，ColorPicker用于颜色选取，日期和时间控件处理日历和时钟功能，Dialogs和Flyouts用于弹出式界面，Flipview实现滑动浏览，Hub用于组织内容，Hyperlinks处理链接跳转，Images和ImageBrushes用于显示图像，InkingControls支持手写和绘图功能，还有列表视图、进度条、滑块等多种控件，满足各类应用场景的需求。 "UWP编程宝典"不仅涵盖了从入门到进阶的全部内容，还深入探讨了设计和用户体验的各个方面，是UWP开发者不可或缺的参考资料。通过学习这本书，你将能够创建出既美观又功能丰富的UWP应用程序，覆盖广泛的Windows 10设备用户。

Let's get started

More advanced topics

Use sale prices for apps and add-ons.

In-app purchases and ads are also available.

For a more detailed look at the UWP, read the Guide to Universal Windows Platform apps. Then, check out Get set

up to download the tools you need to start creating apps, and then write your first app!

.NET Native - What it means for Universal Windows Platform (UWP) developers

Universal Windows apps in .NET

.NET for UWP apps

Intro to the Universal Windows Platform

7/5/2017 • 19 min to read • Edit Online

Device families

In this guide, you'll learn about the Universal Windows Platform (UWP) and Windows 10:

What a device family is and how to decide which one to target.

What an Extension SDK is and how it provides access to APIs specific to a class of devices.

New UI controls and panels for adapting your UI to different screen sizes or rotations.

How to understand and control the API surface that is available to your app.

Windows 10 introduces the Universal Windows Platform (UWP), which provides a common app platform available

on every device that runs Windows 10. The UWP provides a guaranteed core API across devices. This means you

can create a single app package that can be installed onto a wide range of devices. And, with that single app

package, the Windows Store provides a unified distribution channel to reach all the device types your app can run

on. Apps that target the UWP can call not only the WinRT APIs that are common to all devices, but also APIs

(including Win32 and .NET APIs) that are specific to the class of device that the app is running on.

Because your UWP app runs on a wide variety of devices with different form factors and types of input, you want it

to be tailored to each device and be able to unlock the unique capabilities of each device. In addition to the

guaranteed core API layer, you can write code to access device specific APIs so that your app lights up features

specific to one type of device while presenting a different experience on other devices. Adaptive UI controls and

new layout panels help you to tailor your UI across a broad range of device screen resolutions and sizes.

In order to understand how Windows 10 allows you to target different classes of devices, it's helpful to understand

a concept called device families. A device family identifies the APIs, system characteristics, and behaviors that you

can expect across a class of devices. It also determines the set of devices on which your app can be installed from

the Store. A device family (with the exception of the Universal device family) is implemented as an extension SDK,

which we will discuss shortly. Here is the device family hierarchy.

A device family defines a set of APIs and is versioned. A device family is the foundation of an OS. PCs and tablets

run the desktop OS, which is based on the desktop device family. Phones run the mobile OS, which is based on the

mobile device family.

Each child device family adds its own APIs to the ones it inherits. The resulting union of APIs in a child device family

is guaranteed to be present in the OS based on that device family, and on every device running that OS.

One benefit of the universal device family is that your app can run on any, or even all, of a variety of devices from

phones, tablets, desktop computers, Surface Hubs, Xbox consoles, and HoloLens. Your app can also use adaptive

code to dynamically detect and use features of a device that are outside of the universal device family.

The decision about which device family (or families) your app will target is yours to make. And that decision

impacts your app in these important ways. It determines:

The set of APIs that your app can assume to be present when it runs (and can therefore call freely).

The set of API calls that are safe only inside conditional statements.

The set of devices on which your app can be installed from the Store (and consequently the form factors that

you need to consider when you design the UI).

There are two main consequences of making a device family choice: the API surface that can be called

unconditionally by the app, and the number of devices the app can reach. These two factors involve tradeoffs and

are inversely related. For example, a UWP app is an app that specifically targets the universal device family, and

consequently is available to all devices. An app that targets the universal device family can assume the presence of

only the APIs in the universal device family. Other APIs must be called conditionally. Also, such an app must have a

highly adaptive UI and comprehensive input capabilities because it can run on a wide variety of devices. A

Windows mobile app is an app that specifically targets the mobile device family, and is available to devices whose

OS is based on the mobile device family (which includes phones, tablets, and similar devices). A mobile device

family app can assume the presence of all APIs in the mobile device family, and its UI has to be moderately

adaptive. An app that targets the IoT device family can be installed only on IoT devices and can assume the

presence of all APIs in the IoT device family. That app can be very specialized in its UI and input capabilities because

you know that it will run only on a specific type of device.

Extension SDKs

UI and universal input

Here are some considerations to help you decide which device family to target:

Maximizing your app's reach

To reach the maximum range of devices with your app, and to have it run on as many kinds of devices as possible,

your app will target the universal device family. By doing so, the app automatically targets every device family

that's based on universal (in the diagram, all the children of universal). That means that the app runs on every OS

based on those device families, and on all the devices that run those operating systems. The only APIs that are

guaranteed to be available on all those devices is the set defined by the particular version of the universal device

family that you target. To find out how an app can call APIs outside of its target device family version, see Writing

Code later in this topic.

Limiting your app to one kind of device

You may not want your app to run on a wide range of devices; perhaps it's specialized for a desktop PC or for an

Xbox console. In that case you can choose to target your app at one of the child device families. For example, if you

target the desktop device family, the APIs guaranteed to be available to your app include the APIs inherited from

the universal device family plus the APIs that are particular to the desktop device family.

Limiting your app to a subset of all possible devices

Instead of targeting the universal device family, or targeting one of the child device families, you can instead target

two (or more) child device families. Targeting desktop and mobile might make sense for your app. Or desktop and

HoloLens. Or desktop, Xbox and Surface Hub, and so on.

Excluding support for a particular version of a device family

In rare cases you may want your app to run everywhere except on devices with a particular version of a particular

device family. For example, let's say your app targets version 10.0.x.0 of the universal device family. When the

operating system version changes in the future, say to 10.0.x.2, at that point you can specify that your app runs

everywhere except version 10.0.x.1 of Xbox by targeting your app to 10.0.x.0 of universal and 10.0.x.2 of Xbox. Your

app will then be unavailable to the set of device family versions within Xbox 10.0.x.1 (inclusive) and earlier.

By default, Microsoft Visual Studio specifies Windows.Universal as the target device family in the app package

manifest file. To specify the device family or device families that your app is offered to from within the Store,

manually configure the TargetDeviceFamily element in your Package.appxmanifest file.

Once you have decided on the device family that your app will target, add a reference to the Extension SDK(s) that

implements the APIs for that device family. If you are targeting the Universal device family, you don't need to

reference an extension SDK. But if you are targeting a device family besides Universal, in Visual Studio you will add

a reference to the extension SDK that matches the device family you have chosen. For example, if you are targeting

the mobile device family, you would add a reference to the Windows Mobile Extensions for the UWP in Visual

Studio's Reference Manager.

Selecting a device family does not prohibit you from adding extension SDKs for other types of devices. You will just

need to ensure that you test for the presence of APIs not included in the device family you have chosen as

described below in Writing Code.

A UWP app can run on many different kinds of devices that have different forms of input, screen resolutions, DPI

density, and other unique characteristics. Windows 10 provides new universal controls, layout panels, and tooling

to help you adapt your UI to the devices your app may run on. For example, you can tailor the UI to take advantage

of the difference in screen resolution when your app is running on a desktop computer versus on a mobile device.

Universal controls and layout panels

Some aspects of your app's UI will automatically adapt across devices. Controls such as buttons and sliders

automatically adapt across device families and input modes. Your app's user-experience design, however, may

need to adapt depending on the device the app is running on. For example, a photos app should adapt the UI when

running on a small, hand-held device to ensure that usage is ideal for single-hand use. When the photos app is

running on a desktop computer, the UI should adapt to take advantage of the additional screen space.

Windows helps you target your UI to multiple devices with the following features:

Universal controls and layout panels help you to optimize your UI for the screen resolution of the device

Common input handling allows you to receive input through touch, a pen, a mouse, or a keyboard, or a

controller such as a Microsoft Xbox controller

Tooling helps you to design UI that can adapt to different screen resolutions

Adaptive scaling adjusts to resolution and DPI differences across devices

Windows 10 includes new controls such as the calendar and split view. The pivot control, which was previously

available only for Windows Phone, is also now available for the universal device family.

Controls have been updated to work well on larger screens, adapt themselves based on the number of screen

pixels available on the device, and work well with multiple types of input such as keyboard, mouse, touch, pen, and

controllers such as the Xbox controller.

You may find that you need to adapt your overall UI layout based on the screen resolution of the device your app

will be running on. For example, a communication app running on the desktop may include a picture-in-picture of

the caller and controls well suited to mouse input:

However, when the app runs on a phone, because there is less screen real-estate to work with, your app may

eliminate the picture-in-picture view and make the call button larger to facilitate one-handed operation:

To help you adapt your overall UI layout based on the amount of available screen space, Windows 10 introduces

剩余5878页未读，继续阅读

atnanhua5

粉丝: 2
资源: 7

UWP编程全方位指南

Matrix-UWP: 探索UWP在矩阵客户端中的应用

libsodium-uwp：UWP平台上安全加密库的应用

UWP Succinctly: 开发跨平台应用指南

c#&编程实战宝典&本书源文件

C#经验技巧宝典C#由浅入深教你学会C#编程

C#技巧宝典光盘源码

C#开发经验技巧宝典

Microsoft Mobile 移动开发宝典

Java .net 面试葵花宝典

C#程序开发范例宝典好

最新资源