C#4深度探索：Pro Silverlight 5实战指南

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

《Pro Silverlight 5 in C# 第4版》是一本深度讲解Microsoft Silverlight 5技术的权威指南，专为C#开发者设计。该书以C# 4作为主要编程语言，从基础知识开始，逐步深入，涵盖了Silverlight 5的核心概念和技术特性。书中首先在第1章介绍了Silverlight 5的概述，帮助读者对平台的基本架构、目标和用途有全面了解。接着，第2章详细讲解了XAML（Extensible Application Markup Language），它是Silverlight中用于描述用户界面的关键语言，通过实例演示如何构建和组织UI元素。布局设计是第3章的重点，讲述了如何利用Dependency Properties和Routed Events实现灵活的界面响应。第4章进一步深化了对依赖属性和路由事件的理解，这些都是实现组件交互和动态调整的基础。第5至15章分别深入到Silverlight中的各种关键元素、应用程序模型、导航、图形和变换、绘图工具（如Brushes、位图和打印功能）、动画基础与高级技术、多媒体处理（包括声音、视频和DeepZoom技术）、3D图形以及样式、行为和控件模板的设计。这些章节不仅理论详尽，还包含丰富的实践案例，帮助读者掌握实际应用技巧。多线程编程在第16章探讨，这对于优化用户体验和提高性能至关重要。第17章则关注浏览器集成，讨论如何确保Silverlight应用程序与宿主环境无缝协作。对于离线和桌面应用程序的支持，第18章提供了深入的探讨。第19章转向服务端通信，介绍了如何通过ASP.NET Web Services与后端数据进行交互。数据绑定和管理是至关重要的，因此第20章详细讲解了数据绑定技术，包括数据绑定的基础和高级用法。第21章专门讲述数据控件，展示了如何使用它们来展示和操作数据。最后，第22章总结了全书所学，通过实例展示如何将所有知识点整合，构建完整的应用程序。《Pro Silverlight 5 in C# 第4版》不仅适合初学者系统学习Silverlight 5，也适合经验丰富的开发人员提升技能和更新知识，无论是在设计美观的界面、高效的数据管理，还是实现跨平台的应用扩展，都能从中找到所需的专业指导。

CHAPTER 1  INTRODUCING SILVERLIGHT

(and download a beta) from www.microsoft.com/visualstudio/lightswitch. Or, check out Pro Business

Applications with Silverlight 5 (Apress, 2011), which has a dedicated chapter on the subject.

Visual Studio vs. Expression Blend

If you’re still trying to understand how Visual Studio and Expression Blend stack up, here’s a quick

overview:

• Visual Studio: It has everything you need to develop Silverlight applications, with a

visual designer for Silverlight pages. Using this designer, you can drag, drop, and

draw your user interface into existence (which isn’t always the best idea), and you

can get a live preview of what it looks like (which is terrifically useful).

• Expression Blend: It provides the rich support for creating Silverlight user

interface, with visual tools that surpass Visual Studio. For certain types of user

interface grunt work (for example, creating a nice gradient fill), it’s a tremendous

help. Expression Blend also supports a fun application prototyping tool called

SketchFlow and includes a decent coding editor that’s designed to look like Visual

Studio. However, it lacks many advanced and important development tools, such

as debugging, code refactoring, and project source control.

 Note Visual Studio 2010 includes full support for creating Silverlight 3 projects. But to create Silverlight 5

projects, you need the Silverlight 5 Tools for Visual Studio 2010. And if you plan to use Expression Blend with

Silverlight 5, you’ll (currently) need to use a beta version called the Expression Blend Preview for Silverlight 5. You

can download both tools from the Microsoft Download Center (search for Silverlight 5 at

www.microsoft.com/download).

This book assumes you’re working primarily with Visual Studio. You’ll get occasional tips for

Expression Blend (and other Expression products that work with Silverlight, including the Expression

Design drawing tool and Expression Encoder video encoding tool). But if you really want to master

Expression Blend, you should consider a dedicated book on the subject, spend an afternoon

experimenting, or take a look through Microsoft’s Expression Blend training videos at

http://expression.microsoft.com/cc136535.aspx.

Understanding Silverlight Websites

You can create two types of Silverlight websites in Visual Studio or Expression Blend:

• An ordinary website with HTML pages: In this case, the entry point to your

Silverlight application is a basic HTML file that includes a Silverlight content

region.

CHAPTER 1  INTRODUCING SILVERLIGHT

• ASP.NET website: In this case, Visual Studio creates two projects—one to contain

the Silverlight application files and one to hold the server-side ASP.NET website

that will be deployed alongside your Silverlight files. The entry point to your

Silverlight application can be an ordinary HTML file, or it can be an ASP.NET web

page that includes server-generated content.

So, which approach is best? No matter which option you choose, your Silverlight application will

run the same way—the client browser will receive an HTML document, which will include a Silverlight

content region, and the Silverlight code will run on the local computer, not the web server. However, the

ASP.NET web approach makes it easier to mix ASP.NET and Silverlight content. This is usually a better

approach in the following cases:

• You want to create a website that contains both ASP.NET web pages and

Silverlight-enhanced pages.

• You want to create a Silverlight application that calls a web service, and you want

to design the web service at the same time (and deploy it to the same web server).

• You want to generate Silverlight content indirectly, using specialized ASP.NET

web controls.

On the other hand, if you don’t need to write any server-side code, there’s little point in creating a

full-fledged ASP.NET website. Many of the Silverlight applications you’ll see in this book use basic

HTML-only websites. The examples only include ASP.NET websites when they need specific server-side

features. For example, the examples in Chapter 20 use an ASP.NET website that includes a web service.

This web service allows the Silverlight application to retrieve data from a database on the web server, a

feat that would be impossible without server-side code. You’ll learn how to design an ASP.NET web

service for Silverlight in Chapter 19.

ADDING SILVERLIGHT CONTENT TO AN EXISTING WEBSITE

A key point to keep in mind when considering the Silverlight development model is that in many cases

you’ll use Silverlight to augment the existing content of your website, which will still include generous

amounts of HTML, CSS, and JavaScript. For example, you might add a Silverlight content region that

shows an advertisement or allows an enhanced experience for a portion of a website (such as playing a

game, completing a survey, interacting with a product, or taking a virtual tour). You may use Silverlight-

enhanced pages to present content that’s already available in your website in a more engaging way or to

provide a value-added feature for users who have the Silverlight plug-in.

Of course, it’s also possible to create a Silverlight-only website, which is a somewhat more daring

approach. The key drawback is that Silverlight isn’t installed as widely as other web technologies such as

Flash, and doesn’t support legacy clients such as those running the Windows ME or Windows 2000

operating system. As a result, Silverlight doesn’t have nearly the same reach as ordinary HTML. Many

businesses that are adopting Silverlight are using it to distinguish themselves from other online

competitors with cutting-edge content, but they aren’t abandoning their traditional websites.

CHAPTER 1  INTRODUCING SILVERLIGHT

• App.xaml and App.xaml.cs: These files configure your Silverlight application. They

allow you to define resources that will be made available to all the pages in your

application (see Chapter 2), and they allow you react to application events such as

startup, shutdown, and error conditions (see Chapter 6). In a newly generated

project, the startup code in the App.xaml.cs file specifies that your application

should begin by showing MainPage.xaml.

• MainPage.xaml: This file defines the user interface (the collection of controls,

images, and text) that will be shown for your first page. Technically, Silverlight

pages are user controls—custom classes that derive from UserControl. A Silverlight

application can contain as many pages as you need—to add more, simply choose

Project

 Add New Item, pick the Silverlight User Control template, choose a file

name, and click Add.

• MainPage.xaml.cs: This file includes the code that underpins your first page,

including the event handlers that react to user actions.

 Note For the first few chapters of this book, you’ll create applications that have just a single page. In Chapter 6,

you’ll take a closer look at the application logic that sets your initial page. In Chapter 7, you’ll break free of this

constraint altogether and learn the techniques you need to combine pages and navigate from one to another.

Along with these four essential files, there are a few more ingredients that you’ll find only if you dig

around. Under the Properties node in the Solution Explorer, you’ll find a file named AppManifest.xml,

which lists the assemblies that your application uses. You’ll also find a file named AssemblyInfo.cs,

which contains information about your project (such as its name, version, and publisher) that’s

embedded into your Silverlight assembly when it’s compiled. Neither of these files should be edited by

hand—instead, they’re modified by Visual Studio when you add references or set project properties.

Last, the gateway to your Silverlight application is an automatically generated but hidden HTML test

page named ProjectNameTestPage.html. So if your project is SilverlightApplication1, that page is named

SilverlightApplication1TestPage.html (see Figure 1-3). To see this file, make sure you’ve compiled your

application at least once. Then, click the Show All Files button at the top of the Solution Explorer, and

expand the Bin\Debug folder (which is where your application is compiled). The test page file includes

an <object> element that creates the Silverlight content area. You’ll take a closer look at it later in this

chapter.

剩余969页未读，继续阅读

Matchh

粉丝: 3
资源: 1

C#4深度探索：Pro Silverlight 5实战指南

Pro Silverlight 5 in CSharp 4th edition

Apress Pro ASP.NET 4 in CSharp 2010 4th Edition Jun 2010

Pro Silverlight2 in CSharp 2008

MacDonald's Pro.Silverlight 5 in C# 4th Edition: Unleashing Full Potential

Apress.Pro.Silverlight.5.in.CSharp.4th.Edition

C#4th Edition: Pro.Silverlight.5权威指南

Apress.Pro.CSharp.2010.and.the.dotNET.4.Platform.5th.Edition.May.2010.pdf

Programming C# 4.0 6th Edition

精通Silverlight 5：C#版

C#实战：Silverlight 5开发详解

最新资源