C#与XAML打造专业Windows 8.1应用开发指南

5星 · 超过95%的资源需积分: 9 113 浏览量更新于2024-07-22 收藏 12.98MB PDF 举报

"Pro Windows 8.1 Development with XAML and C#" 是一本专注于在Windows 8.1平台上使用XAML（Extensible Application Markup Language）和C#语言进行应用开发的专业指南。该书旨在帮助开发者们利用已有的Windows Presentation Foundation (WPF) 开发经验，因为这两种技术在Windows 8.1应用程序设计中有许多共同点，如利用XAML构建用户界面和使用C#编写程序逻辑。在本书的第一章“Getting Started”，读者将被引导进入Windows 8.1开发的世界，了解其与传统WPF开发的相似之处，包括如何利用XAML创建动态、响应式的UI元素，以及如何通过C#处理控件的行为和交互。尽管有共同点，但也会强调Windows 8.1特有的差异，比如针对触摸屏优化的设计原则和全新的Metro风格用户界面。第二章至第十章分别深入探讨了关键的主题：从构建第一个Windows 8.1应用程序开始，逐步介绍主题、面板、控件的设计与实现，数据绑定的概念和应用，以及如何处理本地和远程数据、服务的集成。书中会涉及搜索和分享功能的合同设计，通知系统的使用，以及应用程序生命周期管理，这些都是现代Windows应用必不可少的功能。第十一章“Making Money”着重于盈利模式，包括应用内购买、广告收入和Windows Store的商业模式，这对于开发者来说是至关重要的商业策略部分。最后，章节“Publishing Your App”涵盖了发布流程，包括如何准备应用以便通过Windows Store分发，遵循审核标准，以及推广策略，确保你的应用程序能够成功进入市场。这本书提供了一个全面的框架，帮助读者从入门到精通Windows 8.1应用程序开发，无论是对WPF熟悉的老手，还是初次接触此领域的开发者，都能从中受益匪浅。通过结合丰富的实例和实用的技巧，作者力图使读者能够高效地掌握XAML和C#在Windows 8.1环境中的应用开发实践。

CHAPTER 1 ■ GETTING STARTED

That’s a lot of windows, but at least in the default layout (much like Visual Studio, you can change the layout to

suit your needs). Let’s look at them in a little more detail.

Projects, Assets, States, and Device Tabs

The top-left corner of the window contains the Projects, Assets, States, and Device tabs, which allow you to do the

following processes:

The Projects tab shows all of the files in your solution (much like Solution Explorer in Visual •

Studio). Nothing too exciting to report here.

The Assets tab lists all of the assets available to add to your page. Think of this as a •

turbo-charged Visual Studio Toolbox. In addition to controls and panels that you can add to

your page, you can also add (and modify) styles, behaviors, and media.

The States tab allows you to add the Visual State Manager XAML as well as Visual State groups •

to your page. It also allows for easy addition of transitions for your visual states.

The Device tab allows you to change the resolution and orientation as well as connected edges •

(more on this in subsequent chapters). You can also change the theme (between light and

dark) as well as the minimum width.

Objects and Timeline

The Objects and Timeline panel (lower left) provides the document outline as well as the ability to add and modify

storyboards (to be used in conjunction with the Visual State Manager).

Figure 1-8. MainPage.xaml opened in Blend

CHAPTER 1 ■ GETTING STARTED

Page Designer, Markup, and Code

The center of the workspace is the designer and code editor. Just like in Visual Studio, you can have a split view, all

design, or all markup. You can also load code files into the center pane. While you get features like Intellisense, the

development experience doesn’t contain all of the great features of Visual Studio like navigation and refactoring.

Plus, you lose any productivity plug-ins like Telerik’s JustCode that you might have installed in Visual Studio.

Properties, Resources, and Data Tabs

The right rail of the workspace contains the Properties, Resources, and Data tabs, which can be described as follows:

The Properties tab is where I spend a significant portion of my time in Blend. In addition to •

the simple items like Name and Layout and properties like Width and Height, there are a host

of properties that are difficult to set by hand in markup. Brushes, Transforms, and Interactions

can all be set using the Properties panel.

The Resources tab contains all of the application and page-level resources as well the option •

to edit and add more resources.

The Data tab allows you to set the data context for your page, create sample data, and create •

different data sources. This is helpful to see what the page will look like with data at design

time instead of always having to run the app.

Blend for Visual Studio is an extremely powerful tool and it would take an entire book to discuss all of the

features. My development workflow involves keeping both Visual Studio and Blend open at the same time, and I

switch back and forth depending on what I am trying to accomplish. Explore Blend, and see what works best for you.

Git

Software version control has been around for a long time. If you have been in the Microsoft space for a significant

length of time, you might remember Visual Source Safe. In the .NET world, the MS developer was left with Team

Foundation Server (TFS) as the only integrated source-code-management (SCM) system.

TFS is a powerful application lifecycle management (ALM) tool (including project management, bug tracking,

SCM, and other components). That is a lot of tooling when you are only looking for SCM. The SCM portion of TFS is

Team Foundation Version Control (TFVC) and is a centralized SCM system. This means that a single repository is the

source of record, and all developers check their code in and out of this single repository. Later versions of TFVC have

included the capability to shelve work and create branches, providing some isolation for work in progress.

Git, developed by Linus Torvalds in 2005 for the Linux kernel, is a distributed version control system (DVCS). This

means that every developer using Git has a full-fledged repository on his local machine with complete history and

tracking capabilities. Many Git users (especially in a team environment) have a central repository in addition to their

local repository. This frees the developer to spike different ideas, work on features independent of the rest of the team,

and check in rapidly as often as they like without worrying about network latency or affecting other team members.

Which SCM system you choose to use is completely up to you. They both have their merits (and there are many

other SCM systems available to you as well that are very effective in what they do). It’s more how you work and whom

you work with that usually determines which system to use. So why do I bring up Git specifically in this book? Because

if you are a single developer creating a Windows 8 app, Git is custom tailored to you, and with Visual Studio 2013

(and updated to Visual Studio 2012), Git support is now included.

There are entire books written about effectively using Git, so this is just a quick look into the Visual Studio

integration, and not a treatise on DVCS.

Using Git in Visual Studio

One of the advantages of using Git is its simplicity. A Git repository can be created anywhere—on a local disk, network

share, or web site (like GitHub).

剩余334页未读，继续阅读

hahahoo

粉丝: 1
资源: 5

C#与XAML打造专业Windows 8.1应用开发指南

Pro Windows 8.1 Development with XAML and C#的例子源码

Windows SDK 8.1离线包

Windows 8.1开发指南：XAML与C#实战

windows 8.1 sdk 百度云下载.rar

WIN8.1 SDK

windows phone 开发书籍及资料

Windows Phone 8.1 开发入门教程

上市公司企业澄清公告数据（2001-2023年） .xlsx

(源码)基于Java和MySQL的物联网环境监测系统.zip

中国2002-2021年31省份经济韧性测度三级指标数据【重磅，更新！】

最新资源