精通Silverlight 5：C#版

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

"Apress.Pro.Silverlight.5.in.CSharp.4th.Edition.Jan.2012" 是一本面向专业开发者的教程，详细介绍了如何使用C#进行Silverlight 5开发，以创建丰富的网页用户体验。这本书涵盖了Silverlight的新特性，包括对H.264视频的支持、图形引擎的重大改进（包括真正的3D渲染）以及更强大的数据绑定选项，使其能与其它应用程序无缝对接。在本书中，你可以学习到： 1. 跨浏览器和平台开发富媒体应用，利用Silverlight的优势。 2. 创建项目，设置布局，使用控件。 3. 通过Windows Presentation Foundation (WPF)处理2D和3D绘图、动画和媒体播放。 4. 集成web服务支持，实现Silverlight与ASP.NET的协同工作以及与HTML的交互。 5. 掌握样式、行为、模板和自定义控件的使用。 6. 学习浏览器集成、ASP.NET、Web服务、数据绑定、数据控件、文件访问、多线程、网络以及离线应用的开发。本书适合初次接触Silverlight的.NET开发者，无需预先了解WPF或ASP.NET。目录结构包括： 1. 引言Silverlight。 2. XAML语言基础。 3. 布局管理。 4. 依赖属性和路由事件。 5. 元素操作。 6. 应用程序模型。 7. 导航框架。 8. 形状和几何图形。 9. 刷子、位图和打印。 10. 动画基础。 11. 高级动画。 12. 音频、视频和Deep Zoom功能。 13. Silverlight 3D技术。 14. 样式和行为。 15. 控件模板。 16. 多线程编程。 17. 浏览器集成。 18. 离线应用程序开发。 19. ASP.NET Web服务。 20. 数据绑定原理。 21. 数据控件的使用。 22. 更多高级主题。通过这本全面的教程，读者将深入理解.NET技术，并能熟练运用Silverlight开发下一代Web应用，与Adobe Flash竞争。

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页未读，继续阅读

KevinWu2019

粉丝: 1

精通Silverlight 5：C#版

C#实战：Silverlight 5开发详解

《Apress.Pro.Expression.Blend.4》：精通微软WPF与Silverlight开发的全面指南

银光5.0 C#实战指南：从入门到精通

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

Apress.Pro.ASPNET3.5.in.C.Sharp.2008.Includes.Silverlight2.3rd.Edition.Jan.2009 part 3-2

Apress.Pro.ASPNET3.5.in.C.Sharp.2008.Includes.Silverlight2.3rd.Edition.Jan.2009 part 3-1

Apress.Pro.ASPNET3.5.in.C.Sharp.2008.Includes.Silverlight2.3rd.Edition.Jan.2009 part 3-3

Apress.Pro.Business.Applications.with.Silverlight.5.2nd.Edition.2012

Apress.Pro.Business.Applications.with.Silverlight.5.2nd.Edition.Feb.2012

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

最新资源