Silverlight教程下载

附件包括 Essential Silverlight以及Code部分

9月份第一版

书中的部分内容

此书面向的读者

       这本书有两大目标读者：喜欢自学silverlight技术的开发人员，以及期望了解silverlight展现的设计人员。我的兴趣，仍然是站在开发人员这边。很自然，权威指南系列的观念是：你可以立刻安装运行silverlight，看到最重要的理念，并且得到很多的代码实例。
       当前的silverlight有两个可使用的版本，1.0(2007年9月份发布)和1.1(已发布一个alpha版本)。这本书包括silverlight1.0，并对即将发布的版本(将在2008年的某个时候发布)提供简短的预览。Windows Presentation Foundation(WPF)的知识不是必需的，但是如果你已经使用过它，意味着你已经拥有了一些silverlight基础。从编程的一个角度看，JavaScript是一种可选择的语言，假如你之前没有使用过它，查阅O'Reilly目录，可以获得更好的选择。

此书的编写结构

第一部分 关于Silverlight以及相关技术的背景资料

第一章

介绍Windows Presentation Foundation(WPF)以及与Silverlight的关系

第二章

执行所有需要的安装步骤并且创建你的第一个Silverlight程序

第三章

查看可辅助更加容易地创建Silverlight内容的软件。

第二部分

未完待续..

翻译中出现的问题，请大家指证。(转载注明译者www.mdong.org langmuir)

只想传达旋律奏响的瞬间
好像把小小的手紧紧包住
只要有你在风就会继续吹拂
不知何时孤单一人在迷失了时间的夜里
让我告诉你
水面闪耀着的奇幻的光
被感染的心灵是看不见的繁星光辉
我在想着你
回望着被终止的过去
这样我就能看到天空

What Changed Between Beta and Release of Silverlight 1.0

This document provides a list of new features, changes, and enhancements that have been made to Silverlight since the Silverlight 1.0 Beta release (MIX release May, 2007). In addition, this document provides a list of "breaking changes" that you might need to make in applications that you created using the Silverlight 1.0 Beta release, in order to make them compatible with the Silverlight 1.0 release.

Note: Another resource for breaking changes is here.

This overview covers the following topics:
Silverlight 1.0 Release Enhancements
Breaking Changes
Remove "javascript:" in event handlers
Remove "Sys."
Use the latest Silverlight.js
All Downloads are now Asynchronous
Glyph element FontURI is Resolved Asynchronously
Remove Visibility.Hidden
Extra check on ASX Tags Resulting in MediaFailed Event
New Parser Error on Invalid Double Values like "Auto"
OnLoad, OnError, OnResize, OnFullScreenChange are now Function Pointer Based Rather than String Based
Elements in <*.Resource> blocks must be named
The MediaElement Position property value can be greater than the MediaElement NaturalDuration property value
Additional Animation Run-Time Errors
Can No Longer Use ’\’ in URIs
All Shaped Transform Members are now of Type Transform instead of TransformGroup
Remove IsFilled Property
AddEventListener now Returns a Token to be Passed to removeEventListener to Un-Register Event Handlers
Replace <control>.settings.version Property with isVersionSupported method
Change enableHtmlAccess: true to enableHtmlAccess: "true"
The width and height properties in createObject must be string values
Tighter restrictions of what objects can have child objects
Downloader is only able to make a download from the same port as the HTML
Silverlight 1.0 Release Enhancements

New "root" property on Content. Enables access to the root element of the XAML DOM.
New “Tag” property on UIElement. Enables user storage on every Silverlight UIElement.
New MediaElement APIs for selecting different audio streams out of a file with multiple audio tracks. See the AudioStreamCount and AudioStreamIndex properties.
Improved media performance: optimized assembly instructions for the video decode.
Media script commands encoded in a separate stream in the video file will now raise the MediaElement’s MarkerReached event.
Added support for Adobe CFF fonts.
Improved performance for transparent controls on Safari.
Breaking Changes

The following list contains the breaking changes between the release of Silverlight 1.0 and Silverlight 1.0 Beta (Mix release of May, 2007). If you have created applications using the Beta release, please update your applications using this list as a guideline. Use the code samples, where provided, to ensure your application runs on both Beta and RTM version of Silverlight 1.0.
Remove "javascript:" in event handlers

The first example shows attaching an event handler in Beta and the second example shows how to do it in the 1.0 release.

Silverlight BetaXAML
<canvas onMouseLeftButtonDown="javascript:myhandler"   />

Silverlight ReleaseXAML
<canvas onMouseLeftButtonDown="myhandler" />  

Remove "Sys."

Remove "Sys." from namespaces in your code. For example, change the following beta code. JavaScript
Sys.Silverlight.createObject(....)   

To this code.JavaScript
Silverlight.createObject(....)   

Use the latest Silverlight.js

Please make sure you use the latest Silverlight.js provided to you in your applications. A few changes have been made to this file. The plug-in has been renamed from "WPFe Plug-In" to "Silverlight Plug-In". This plug-in is referred to in Silverlight.js file to detect Silverlight on the system. Also the MIME type of the plug-in was changed from application/ag-plugin to application/x-silverlight. Finally, the namespace "Sys." was removed. Make sure all instances of "Sys." are pulled from your applications.
All Downloads are now Asynchronous

Due to difficulties in providing reliable synchronous downloads across all platforms, we’ve removed this feature from our downloader API. Consequently, the 3rd parameter on the download open API has been removed as it is no longer needed. You must update open calls to remove this parameter.

Only the Beta release lets you add the extra argument to the downloader open method. Following is an example. JavaScript
function download(host, file) {
   var dl = host.createObject("downloader");
   dl.addEventListener("completed", downloadComplete);
   // If Beta version add the extra argument
   if (_mix) {
     dl.open("get", file, true);
   } else {
     dl.open("get", file);
   }
   dl.send();
}

Glyph element FontURI is Resolved Asynchronously

When processing the XAML code, the font specified by the Glyphs FontUri attribute is downloaded separately and asynchronously. This means that text displayed by the Glyphs element will appear once the font is downloaded, in most cases after other content has already appeared.

In Silverlight 1.0, there is no event for Glyphs downloading progress when using the FontUri. To work around this you could use the Downloader object to first request the font file (and thus use the Downloader's progress events to know when Glyphs is downloaded).

Once the Downloader has finished downloading the font, you can then create a Glyphs element with the FontUri by specifying the exact same URI. Since the font is already downloaded, it would not be downloaded again and the Glyphs element should render almost instantaneously.

NOTE: This does make an assumption that the font downloaded will remain in the browser's cache (since this retentive behavior is user and browser specific, this is uncertain) and will be picked up when the Glyphs element attempts to download the same file.
Remove Visibility.Hidden

In order to reduce surface area, Visibility.Hidden was removed from the product. Prior to this change, Visibility.Hidden behaved the same as Visibility.Collapsed. Since Silverlight behavior is functionally similar to the behavior of WPF Visibility.Collapsed, Visibility.Collapsed was retained. To create content that will work consistently between Beta and 1.0, replace all occurrences of "Hidden" in both XAML and script with "Collapsed."

For JavaScript, change this Beta code.JavaScript
sender.findName("fsm").visibility = "Hidden";

To this code.JavaScript
sender.findName("fsm").visibility = "Collapsed";

And for XAML, change this Beta code.XAML
<Canvas x:Name="mask" Visibility="Hidden">

To this code.XAML
<Canvas x:Name="mask" Visibility="Collapsed">

Extra check on ASX Tags Resulting in MediaFailed Event

There is a set of ASX tags that were ignored in the Silverlight Beta release and that now result in a MediaFailed event. These tags are: PREVIEWMODE, BANNERBAR, PARAM, REPEAT, STARTMARKER, ENDMARKER and some MOREINFO tags. Also, if a REF URL fails to open, Silverlight does not fall back to other REFs in the same ENTRY. Instead, a MediaFailed event is raised.
New Parser Error on Invalid Double Values like "Auto"

More parser errors are reported in Silverlight 1.0 RTM. Applications will break now in cases where the developer sets a numeric property to an invalid value. In the Beta release, an invalid value was treated as a 0, but Silverlight 1.0 RTM throws an error when it encounters the same value. The following is an example:XAML
<TextBlock Width="Auto" Text="Created By:" />

“Auto” is not supported in Silverlight 1.0. In the Beta release of Silverlight 1.0, the above example causes the Width to be set to 0. Since the Beta release did not clip TextBlock by Width, this did not impact the application behavior. However, this same example will generate a parser error in Silverlight 1.0 RTM.
OnLoad, OnError, OnResize, OnFullScreenChange are now Function Pointer Based Rather than String Based

We’ve changed OnLoad, OnError, OnResize and OnFullScreenChange to be function-pointer based rather than string based. In order to develop Silverlight content that works on both Beta and 1.0 RTM releases, you need to check the version and develop the application code accordingly. The following is an example using OnResize:XAML
if (Silverlight.checkVersion(_ag, "20416")) {
   // Beta code path – use strings
   _ag.content.onResize = "javascript:onResize";
   ag.content.onFullScreenChange = "onFullScreenChanged";
} else {
   // Release code path – use function pointers
   _ag.content.onResize = onResize;
   _ag.content.onFullScreenChange = onFullScreenChanged;
}

Elements in <*.Resource> blocks must be named

Elements in <*.Resource> blocks must be named. This means you must have an x:Name property for all content in a <*.Resources> section. For example:

Silverlight BetaXAML
<Canvas.Resources>
<Storyboard>
       <!-- Content here... -->
    </Storyboard>
</Canvas.Resources>

Silverlight 1.0 RTMXAML
<Canvas.Resources>
    <Storyboard x:Name="name">
         <!-- Content here... -->
     </Storyboard>
</Canvas.Resources>

The MediaElement Position property value can be greater than the MediaElement NaturalDuration property value

This will mostly be seen in broadcast cases which had previously returned 0 for the Position value but now returns the play time. Developers creating transport controls should be aware of this and the need to clip the media if necessary. For example:

Silverlight BetaJavaScript
// set the slider thumb position in the right range of the track’s width
// assumes position is never greater than media’s naturalDuration
sliderThumb[“Canvas.Left”] = (myME.position.seconds/myME.naturalDuration.seconds)*sliderTrack.width;

Silverlight 1.0 RTMJavaScript
// need to clip the slider position by the track’s width
if (myME.position.seconds >= myME.naturalDuration.seconds)
    sliderThumb[“Canvas.Left”] = sliderTrack.width;
else
sliderThumb[“Canvas.Left”] = (myME.position.seconds/myME.naturalDuration.seconds)*sliderTrack.width;

Additional Animation Run-Time Errors

Silverlight 1.0 RTM is stricter than Beta in throwing run-time errors caused by functionality that is not supported. Examples of such errors are:
Storyboard.TargetProperty must be defined on all animations by the time they are begun. Storyboard.TargetName must either be specified on animations themselves or on a parent Storyboard by the time they are begun.
Certain Storyboard/Animations properties can only be modified when the Storyboard is stopped. These properties are Storyboard.TargetName and Storyboard.TargetProperty.
Can No Longer Use ’\’ in URIs

This behavior has been changed in order to maintain the cross platform support of Silverlight-based applications. All Web resources should be renamed if they include a "\". For example, use "./assets/images/bg.jpg" instead of ".\assets\images\bg.jpg”
All Shaped Transform Members are now of Type Transform instead of TransformGroup

This behavior has been changed in order to be consistent across Silverlight and WPF. For example, RTM brush.relativeTransform.toString() will return "Transform" rather than "TransformGroup."
Remove IsFilled Property

The IsFilled property on PathFigure is no longer supported. Developers should remove it from their application code.

Silverlight BetaXAML
<PathFigure IsFilled="true" .../>

Silverlight 1.0 RTMXAML
<PathFigure .../>

AddEventListener now Returns a Token to be Passed to removeEventListener to Un-Register Event Handlers

If you intend to remove event handlers during the lifetime of your Silverlight-based application, you must change the syntax by which you add the event handlers, and retain a token that is now necessary for the removeEventListener call. The token differentiates for cases where multiple handlers were attached for the same event. If you do not intend to remove event handlers, you can leave your addEventListener calls alone, although you should note that addEventHandler now also supports adding the handlers by reference rather than by a quoted name string. This change was made in order to make the Silverlight event object model more similar to other scripting object model syntaxes.

For JavaScript, change this Beta code.JavaScript
myObj.addEventListener(“MouseEnter”, myEnterHandler);
myObj.removeEventListener(“MouseEnter”, myEnterHandler);

To this code.JavaScript
var enterToken = myObj.addEventListener(“MouseEnter”, myEnterHandler);
myObj.removeEventListener(“MouseEnter”, enterToken);

And for XAML, change this Beta code.XAML
<... x:Name=”myObj” MouseEnter=”myEnterHandler”/>
JavaScript
sender.FindName(“myObj”).removeEventListener(“MouseEnter”, myEnterHandler);

To this code.XAML
<... x:Name=”myObj” MouseEnter=”myEnterHandler”/>
JavaScript
sender.FindName(“myObj”).removeEventListener(“MouseEnter”, 0);

Replace <control>.settings.version Property with isVersionSupported Method

Use this method to remove the <control>.settings.version property from the object tag and to use a new isVersionSupported method. This method takes a version string (for example, “1.0” or “1.1”) and returns a Boolean indicating whether the plug-in is compatible with the requested version.
Change enableHtmlAccess: true to enableHtmlAccess: "true"

Following is an example of how to add quotation marks to the value of enableHtmlAccess. Change this example.JavaScript
enableHtmlAccess: true

To this.JavaScript
enableHtmlAccess: "true"

The width and height properties in createObject must be string values

The width and height properties in the createObject function call must be string values, not integer values.
Tighter restrictions of which objects can have child objects

Silverlight 1.0 RTM tightens restrictions on which objects can have child objects. For example, Rectangle and TextBlock used could have child objects in Silverlight Beta, but this is no longer allowed.
Downloader is only able to make a download from the same port as the HTML

The Downloader object is only able to make a download from the same port as the HTML file that hosts the Silverlight plug-in.

这种插件系统并非跨平台,每个平台的文件格式都有所不同.(参考http: //developer.mozilla.org/en/docs/Gecko_Plugin_API_Reference:Plug-in_Development_Overview) 比如Flash插件,Windows平台下文件名为NPSWF32.dll,是一个Win32 DLL;Mac OS 9下文件名为Flash Player NP-PPC,也是一个动态链接库类型的文件(OS X下文件名类似,但代码部分格式为Mach-O);Linux下名为libflashplayer.so和flashplayer.xpt,是所谓的共享对象文件,等等.

NPAPI经过长期修正,并由Mozilla牵头增加了新的npruntime脚本API,现在已经相当成熟,现在除了Windows平 台上的IE之外几乎所有浏览器(所有Mozilla/Netscape系浏览器、Opera、Safari、Konqueror等)都使用这种插件架构(IE在5.5SP2以前也曾经通过plugin.ocx ActiveX提供过对NPAPI插件的支持,后因“安全原因”废止). 它是一种纯粹的二进制可执行插件,通常是为了支持网页中出现的<object>和<embed>标签中定义的对象而存在,不会增 加浏览器自身的任何功能.而且由于他们的运行权限和浏览器本身相同,因此一旦出错,就可以将浏览器拖死(比如Quicktime for Windows经常导致Firefox非法操作之类常见问题).在Mozilla系列浏览器中,可以通过输入about:plugins查看所有已经启用 的插件信息.

而Firefox及一切Mozilla程序的所谓扩展,和插件的概念大不一样.Mozilla扩展并不是真正的本地代码,而只是使用JavaScript语言编制,使用和各主要Mozilla程序一样的所谓XUL(一种基于XML的用户界面脚本语言)编制界面,通过XPCOM 的XPConnect API与浏览器实现交互.这样使得它具有相当高的跨平台可用性,而且因为它完全在浏览器的JavaScript引擎中运行,使得浏览器能够控制他们的行 为,减少扩展出错导致整个浏览器出错的可能性.

对XUL的依赖使得它只被Mozilla系浏览器支持,在XUL支持不完全的部分此类浏览器(如K- Meleon)中得不到完整的支持.当然,XUL也是个可移植的平台,甚至有XULRunner这类独立的扩展运行环境的存在.

通常在Mozilla系浏 览器中,扩展能做到的事情非常多,能够显示和控制自己和整个浏览器的用户界面,可以直接使用浏览器的功能实现自身与网络的通讯、可以通过XPCOM对浏览 器的渲染引擎进行操作,其用途远远比插件宽泛.扩展自身是.xpi安装包,包含所有组件文件和安装脚本,安装后一般不是单一的文件.

这两 类插件在能力上都无法真正和ActiveX相比,后者在Windows中神通广大,作用范围遍及整个Win32子系统,而对于前者,插件可以执行浏览器以 外的代码,扩展不能对运行环境外部造成除了浏览器本身功能之外的其它影响.目前恶意的NPAPI插件数量极少,而扩展(Firefox中)目前基本上都是 Mozilla的官方站点提供下载,几乎不可能出现恶意扩展;而大量的ActiveX控件却是所谓的“流氓软件”.

1.提案

一个有经验的设计师，在给客户交稿时，至少会准备三种设计供他选择。
第一：100%自已喜欢的风格，把自我发挥到极至。
第二：50%自己喜欢，50%客户喜欢的风格，各让一半，互相妥协。
第三：0%自己喜欢，完全从客户的要求出发，放弃自己的风格。

有上述三种准备，交稿时，你往往过的会很从容。 没有经验的新手，只给客户一个提案。
你很喜欢，客户不喜欢，观点不同谈不拢，怎么办?找第三者来评价，他通常会顺着客户的方向说，也否定你，这样，2比1，老板说你做的东西不好，打回去重做，当时间紧时，不好的就硬上了，但是老板并不高兴(用了不喜欢的东西)，你也不高兴(虽然你用了我做的,但是你仍然不认可它。)双方都很痛苦。

2.坚持
这个性格是做美编最不需要的特质，但你需要去努力争取，当你努力与客户，与老板沟通后。人家仍然不喜欢时，就应立刻放弃已有的创意，从头再来，坚持是没有用的，因为你不是奥美的名设计师，不是大师，你坚持是没有用的。

3.美工or设计师。
是做一个拼图的美工，还是一个美术设计师。两者差异很大，一个是工人，用手(体力劳动者)，一个是智者，用脑创造(脑力劳动者)。
二流的美工只会堆效果，而好的设计师，通常只用最简单的手法。

4.一个有经验的美编，在接活时，通常要问几个问题。
第一：做什么用(海报，易拉宝，书籍)
第二：以什么为主题，要突出什么重点，更多了解产品信息(什么年龄的人消费，在同类产品中的地位，以什么为传播媒介)
第三：要明确，客户可以提供什么资料(比如logo，等必要因素)，要明确要自己额外找哪些素材，可以适合产品的背景。
第四：什么时候交稿(这是最重要的问题)
在做之前的准备工作，比上机动手要重要很多，就像走错了方向，走的再远也是白费。

5.老板要求你三天交稿
通常老板要求你三天交稿时，你可以只给他70分的作品。如果你说，老板，我三天做不完，要四天做完。那么第四天，老板要看到的是85分的作品。

6.你的特长是什么？(当老板问美编)
当老板这样问你时，你怎么回答？我说网页。
老板笑了说，这就好比我问你爱吃什么？你答，食物。
我又问什么食物？你答，中国菜。我还是不知道你爱吃什么。
你如果直说，爱吃辣的，水煮鱼，麻婆豆腐……那我就一下子知道你爱吃什么了。
回到原题，特长是风格的问题。
你可以说，我擅长做卡通的风格，现代的风格，传统的风格……

7.聪明的面试者
曾有一个人来面试美编，他准备了把他的作品分成了两类，他喜欢的(代表了他的风格)；他做过的(代表了他的水平) ，美编是个很主观的工作，说好就好，说不好就不好，对于作品，没有衡量的标准。

8.做了半年的美编，我烦了，想转行
在学校时曾经很喜欢这行，梦想就是做在办公室里，每天设计东西，每天都是不一样的。
可是自己从工作以后，越来越烦了，甚至一坐到电脑前，心就开始烦。 老板说，知道为什么吗？因为上学时没人骂你，到公司以后，人家都说你做的东西不行，没有认同，缺乏成就感，所以你烦了。
我说，我怕做这行做到一定时候会有瓶颈，没有大发展。
老板说，做每一行都会遇到瓶颈，只是别的行你还没做过，还没发现，所以你就觉得美编是最痛苦的职业了。
我说，我不喜欢每天只是做在电脑前面。一天不动。
老板说，谁让你一天做在哪里？是你自己，你可以在做之前画个草稿，拿着草稿跟你的老板，客户去沟通，不要急着在电脑上定稿，这就是一个互动的过程!

9.一个美编的职业道路
a：毕业后先进专业性的大广告公司，开拓眼界，积累经验，找个高人(可能带你的人)，或可以向重多的优秀同事学习。
b：然后到非专业的公司，做专业性的工作或部门经理。
c：最后自己跳出来，独立门户，自己接活。(客源是个问题，开始自己带来一些客源，专心设计，客户满意，后来为了多挣些钱，把生产跟印刷都包下来了，分散了太多的精力，导致设计水平下降了，客户不满意，把客户做死，没活了……)
d：最后没办法，只好再从公司做起，现在就可以做到大公司的创意总监。

10.人的一生，需要一个导师
这个人需要具备两个条件。
A：年龄一定要比你大。
B：事业上一定要有所成就。
(有了上述这两点时，是不是同一个领域的，就都无所谓了。)
当你把你工作上的难题向你的同学倾诉时，他们通常会说(老板都一样的，没事，走，晚上一起唱歌去吧。)对你不会有任何的帮助。
而一个好老师需要好学生，好学生需要问好的问题。
我问你想要什么?怎么得到……这样答案都是自己给的。

11.对未知的事物或人，不要忙着拒绝。

很多东西并不仅仅局限于某个行业，从一些文字中更提炼出一些做人的道理，受益匪浅。

EnergySourec 安瑞索思中国
http://www.energysource-cn.com/
目前中国市场上最大，也最有竞争力的互动公司之一。主要客户PHILIPS，上海大众，强生等

CCS
http://www.commcentral.com/
香港地产业巨头在内地收购了lemon多媒体，adxplorer以及整合其他两家做数据平台和媒介方面的公司，MEDIA3WAY、智马后组成的公司~

Made For china
http://www.madeforchina.com/
主要做EDM的公司，但伴随EDM，也做一些小站点~不算非常专门的互动公司~

网帆
http://www.wangfan.com/
主要客户为GM中国旗下的BUICK和雪佛来。做过一段时间的PIZZAHUT。设计能力不错~

上海IDES互动
http://www.idescn.com/
目前在下所在的公司~不做任何评价。

七彩空间
http://www.qicaispace.com/
提供多种交互服务及相关课件的制作.

奥美互动（北京）
http://www.ogilvy.com.cn/
看仔细是北京公司，不是上海，背靠奥美这个大树，奥美虽然不是专门做互动的公司，不过奥美北京的互动部门还是做了很多拿的出手的东西的，像以前的M-ZONE，创意英国等等~

FROM-ZERO
http://www.from-zero.com/
主要客户是ADIDAS、美宝莲~详细情况不了解，待补充

实力传播
http://www.zenithmedia.com.cn/
详细情况不了解，待补充

秀网
http://www.showone.com.cn/
主要客户兰蔻~详细情况不了解，待补充

华扬联众
http://www.hylzad.com/
北京的本地非4A广告公司，主要是做媒介购买，当然也做互动制作方面的东西，但不是赢利点，目前在上海有分公司

纽艾互动
http://www.newitech.net/
主要是做一些ONLINE FLASH GAME的公司~详细情况不了解，待补充

三子科技
http://www.trio.to/
台资的互动公司~详细情况不了解，待补充

P2ART
http://www.p2art.com/
做房产推介站点的新公司，主要客户是万科

北京数码互动
http://www.imcchina.com/
北京的互动公司~详细情况不了解，待补充

FM play
http://www.fmplay.com
不是非常专门的互动公司，但是在互动方面有很多不错的作品。主要是做传媒的~就是娱乐圈啦，呵呵

01media
http://www.01media.cn
这个相信很多人都熟悉，01KKK原来是以工作室形式存在的，后来注册成为了公司，原来主要是做一些传统广告公司的站点，目前又有做一些游戏方面的站点了，如SEGA中国，WOW中国站点，还有东星中国的站点~

2B studio
http://www.framebrain.com/
相信也很多人熟悉，呵呵，梵天兄的公司，新组建~目前在内部调整中~以房产推介为主~期待他们的新消息~

Visual Studio 2008 support
The Expression Blend 2 September Preview can open and work with Microsoft® Visual Studio® 2008 (formerly known as Microsoft Visual Studio code name "Orcas") Beta 2 projects and solutions. By default, Windows Presentation Foundation (WPF) projects that are created in the Expression Blend 2 September Preview are now Visual Studio 2008 projects, if Microsoft .NET Framework 3.5 is installed and such projects cannot be edited in Visual Studio 2005. The Expression Blend 2 September Preview can still open projects that were created with earlier versions of Expression Blend or Visual Studio 2005.

Making Controls from Existing Objects
The Expression Blend 2 September Preview contains new functionality that lets you refactor (in other words, convert) existing content into a control that can be reused (instantiated). Selected elements, their referenced resources, and referenced animations are refactored into the new control. You must build the project to be able to see and instantiate the new control.

Split View and XAML Editor Improvements
The Expression Blend 2 September Preview lets you view an open document in both Design view and XAML view at the same time by selecting the new Split tab on the right side of the artboard. Additionally, you can specify font size, font family, tab size, and word-wrap for the XAML editor (XAML tab) by modifying the Code Editor settings under Options in the Tools menu.

Storyboard Picker
The Storyboard Picker replaces the old Storyboard box. The picker consists of a label to indicate the name of the selected Storyboard (if a Storyboard is selected), a shortcut menu (available when you right-click the label), a pop-up button (and resulting pop-up menu), and a Close button to close all Storyboards and exit recording mode. Both the shortcut menu and the pop-up menu let you create a New Storyboard, and if a Storyboard is already selected, you can now Duplicate, Reverse, or Delete the selected Storyboard. The shortcut menu also lets you Rename the selected Storyboard. The pop-up menu contains all Storyboards in scope in a multicolumn layout. The pop-up menu can be resized, and its list filtered according to a text box at the top of the list. The Storyboard label serves as the Storyboard selector when you want to modify properties on a Storyboard.

Storyboard and Keyframe Properties
The Expression Blend 2 September Preview contains new functionality for setting properties on Storyboards and on keyframes in the Properties panel. When you have a Storyboard selected, you can change the direction of the animation and change the repeat behavior. When you have one or more keyframes selected, you can change the easing behavior between keyframes by modifying the related key splines graphically, or by setting specific values.

Vertex Animation
The Expression Blend 2 September Preview contains new functionality for animating individual vertices (points and tangents) on a line. Previously, if you modified a vertex when in animation recording mode, the original shape of the object was permanently modified.

Breadcrumb Bar
The Expression Blend 2 September Preview now displays a breadcrumb bar above the artboard, which helps you keep track of where you are in a template hierarchy as you navigate through it, as well as quickly switch editing scopes while you are editing templates and styles in WPF projects. The breadcrumb specifies the object that is selected. If a template can be applied to the object (such as a button), you can click a drop-down arrow in the breadcrumb item to view the actions that can be performed on the object (such as editing a button template). If you have already edited a style or template on the object, the breadcrumb will include additional items that represent the style and template items that you edited earlier. This makes it easy to see which style or template has already been edited on an object, to quickly switch the scope in which you are editing, and to understand exactly where you are as you make changes.

Font Embedding
The Expression Blend 2 September Preview contains new functionality for embedding fonts in your project. Embedding makes sure that the font that you select for your application is the font that users will see when they run your application. Typically, users will already have most of the fonts that you can select in Expression Blend, and therefore you do not have to embed them. If the user does not have your chosen font, a default system font will appear. If you do decide to embed, subset, or otherwise redistribute fonts in your application, it is your responsibility to make sure that you have the required license rights for those fonts. For the fonts that come with Expression Blend, see the Microsoft Software License Terms (EULA.language.rtf) file for full license terms. For other commercial fonts, see the Microsoft Typography web site for information that can help you locate a particular font vendor or find a font vendor for custom work. To embed fonts in an Expression Blend application, you can use the new Font Embedding manager available in the Tools menu and available in the Advanced Properties section under Text in the Properties panel when you select a text control. For more information about how to embed fonts in WPF applications, see Packaging Fonts with Applications on MSDN.

Build Options
When building inside the Expression Blend 2 September Preview, the property $(BuildingInsideExpressionBlend) is set to true. You can use this property in your project or .targets files to change how the project builds when in Expression Blend. For more information about how Visual Studio supports this scenario, see the Visual Studio Integration documentation.

Object Manipulation
We’ve added the ability to uniformly resize and scale multiple selected elements by using resizing handles on the artboard.

     我们共同完成了很多人认为无法完成的工作。在短短的几年里，我们确定了推进微软中华区业务发展的清晰而稳固的战略框架。我们的销售增长了几乎一倍，大中华区的销售收入突破了10亿美元。过去的三年里，在中国大陆，我们将销售(含coverec OEMs)业绩提高了两倍，并为2008财年实现10亿美元的目标做好了准备。我们将未经授权的电脑使用率(CPU)降低了20多了百分点；新雇用了几百名员工；将业务运营扩展到了中国大陆、香港、台湾15个以上的城市。我们还加强了同客户和合作伙伴的关系，不仅在本地区乃至全球改变了人们看待微软的方式。

     最重要的是，我们运用我们的技术帮助中国大陆、香港、台湾许许多多的人改善他们的生活和生计。一路走来。从你们每个人身上，我学到了很多；你们使我无法忘记我在微软经历。

     诚然，变化总会伴随着一些不确定。但是，有一点我坚信不疑，那就是，公司有能力延续我们已经开始了的成功，我们已经制定了经过仔细斟酌的交接计划，并出世界最好的领导团队来完成。我对目前的管理团队及其战略充满信心，毕竟Big Rocks计划已经就为。毫无疑问，在不久的将来，微软大中华区谈论不再是10亿美元的突破，而是50亿美元新纪录的创造。

     今天下午四点，我们将在现代汽车大厦召开全体员工大会介绍我的计划和详细的工作交接方案。最后，我想对微软大中华区的每一位员工表达我深深的谢意，感谢你们的辛勤工作，感谢你们为我们的成功所做的贡献。

陈永正

Tim Chen

英文版：

    【发掘网讯】 I want to share with you some difficult news about my future plans. Later today, I will announce that I have resigned from Microsoft and will be taking a position in a different filed. It is not without a heavy heart that I contemplate leaving the incredible work and extraordinary people that I have been privileged to encounter during my four years at Microsoft.

     Together, we have accomplished what some might have thought could not be done. In a few short years, we have defined a clear and stable strategic framework for Microsoft’s business in the Greater China region. We have nearly doubled sales and have broken through the $1 billion mark in revenue in GCR. In China itself, we have tripled our sales in the last three years. Including those of covered OEMs, and we are posed to hit $ 1 billion in FY08. we have reduced the UPC rate by more than 20%. We have added hundreds of new people and expanded our operations to more than 15 locations across the region. We have strengthened our customer and partner relationships and transformed the way people view Microsoft, not just locally but all around the globe as well.    

     Most importantly, we’ve been able to use our technology to help improve the lives and livelihood of millions of people throughout the Greater China region. I have learned from each of you along the way and you have made my experience at Microsoft one that I will never forget.

     While change always comes with its share of unknowns, there is one thing that I have absolutely no question about, and that is this organization’s ability to continue the great work that we’ve begun. We have a well-thought our transltion plan in place and some of the finest leadership in the team and in our strategy with the Big Rocks plan in place. I have no doubt that in the very near future, Microsoft Greater China region will no longer be talking about breaking through the $1 billion but about the $5 billion mark. J

     At 4 PM today, we will have an all-hands meeting in the Millennium Building to discuss my plans and the transition in more detail. In the meantime, I’d like to express my deep thanks to every one of you in the Microsoft Greater China region for your hard work and for your contribution to our continued success.

                                                                                                  Tim Chen

（2007年9月18日 北京）在如今电脑已普及到千家万户、成为人们日常工作生活的基本工具的数字时代，怎样才能更好地享受工作过程的乐趣、享受激情创意的成果？近日，世界领先的数位板系统和笔感应式数位屏系统制造商Wacom公司在全球同步上市全新设计的数位板——Bamboo Fun，这款面向广大消费用户的通用输入设备外观时尚，操作简单，不仅可以用来在电脑上绘画、涂鸦和书写，还可以修整照片，帮助广大用户提升和丰富在摄影、绘画、网页设计、数码影像等数字创作领域以及文档个性化方面的表现力，创造出自己的缤纷新天地。作为Wacom面向消费市场推出的全新品牌Bamboo 系列的第二款重量级产品，Bamboo Fun不仅为图形图像爱好者提供了一款全新的人机界面交互工具，更为广大的普通电脑使用者提供了一种全新的电脑生活方式。它的推出，必将为我们带来更加丰富的电脑体验。

新推出的Bamboo Fun融合了Wacom在开发直观输入设备方面的丰富经验与创新实力，采用了Wacom专利的无线无源压感笔技术，512级压力感应、精确的定位分辨率、高读取速度，可以很好地满足普通消费用户绘画、修编照片等方面的应用需求。Bamboo Fun人性化的设计周到体贴：不仅符合人体工程学原理，而且在Bamboo Fun数位板设有4个可设定的快捷键，用户可以根据自已的操作习惯，把常用的重复性操作设为快速键；压感笔上设有两个可设定的功能键与支持感压的橡皮擦。快捷键和笔配合使用，能大大提高工作效率，快速获得想得到的结果。Bamboo Fun数位板上的触控环，更是可以协助使用者快速放大/缩小页面、浏览文件。用户还可以利用压感笔的画面移动功能来浏览文件，尽享轻松随意的感觉。

Bamboo Fun外观时尚漂亮，颜色典雅大方。为了提供给广大用户更多的选择，Bamboo Fun提供了小幅面和中等幅面两种型号。小幅面Bamboo Fun的外形尺寸为210.0×194.1×11.2 毫米，活动区域为147.6×92.3毫米；中等幅面Bamboo Fun外形尺寸为280×235.1×11.0 毫米，活动区域为216.5×135.3 毫米。两种型号的数位板均为白色，并且中等幅面的Bamboo Fun还提供一只全新设计的无线无源鼠标，可以配合数位板使用。更加方便用户根据需求，自如地选择笔或鼠标来操作电脑。

不仅在硬件方面全面秉承Wacom产品一贯的高品质，Bamboo Fun还提供丰富的软件工具。两种型号的Bamboo Fun都提供易学易用、功能强大的绘图应用软件Corel Painter Essentials 3；中等幅面的Bamboo Fun还提供相片编修软件Adobe Photoshop Elements 5（Windows）和Adobe Photoshop Elements 4（Mac OS）；小幅面的Bamboo Fun提供Ulead PhotoImpact 12 SE，构建起数字影像理想的硬软件组合平台，让用户轻松享受数字创意的无限乐趣。

Bamboo Fun已经获得了微软“Certisfied for Vista”的认证标识，而且每一款型号都支持苹果机，能够释放强大的笔功能，可以在流行的操作系统（特别是Microsoft Windows Vista和Mac OS）上智能识别手写输入，让用户自如地在文档里进行批注、在电子邮件中进行个性化签名。

小幅面的Bamboo Fun市场报价为780元人民币，中等幅面的Bamboo Fun市场报价为1480元人民币。

关于Wacom

Wacom®和冠成立于1983年，作为世界领先水平的数位板系统和笔感应式数位屏系统的制造商，其无线、无源，具有压力感应的笔输入技术广泛为全球数码产品的客户所使用。亦被称为Penabled®的Wacom的电磁感应技术也提供给那些PC和苹果电脑。现今的许多平板电脑都凭借Penabled先进的技术和可靠性实现了笔输入。在不远的未来，Penabled技术将在移动装置例如智能手机和PDA等的发展中扮演重要角色。

Wacom和冠是一家全球性企业，其总公司Wacom Company Ltd.位于日本，在北美（Wacom Technology Corporation），德国（Wacom Europe GmbH），英国（Wacom Components Europe）中国（Wacom China Corporation)，韩国（Wacom Digital Solutions），澳大利亚（Wacom Australia Pty, Ltd）设立了分公司，并在亚太地区设有多个办事机构。