Silverlight 3 beta is released

ArticleDirectory

• Ensuring that your Silverlight 2 applications work with the Silverlight 3 beta release

Download Microsoft Web platform installer 2.0 Beta

Start the installation package after the download. It will obtain the latest network installation package information.

I was pleasantly surprised to find that Silverlight 3 tools for Visual Studio 2008 SP1 beta can be downloaded.

The details are shown in. Compared with Silverlight 2 tools, we found that Silverlight 3 tools is much smaller and more than doubled in size.

The Silverlight 3 Tools version is upgraded from 9.0.30729.146 of Silverlight 2 tools to 9.0.30729.463.

In addition, we also see the official ASP. net mvc 1.0 version from above.

These two Web components are estimated to be released on mix2009 tomorrow.

However, Microsoft Web platform installer 2.0 Beta was accidentally leaked.

However, the current problem is that vs2008 SP1 in the Simplified Chinese version cannot be installed (tested in person)

The Silverlight 3 documentation has been provided for download.

Silverlight 3 tools for Visual Studio beta can also be downloaded from here

 

After installation on vs2008 SP1 in English version, the Silverlight 3 runtime version is 3.0.40307.0

Silverlight 3 contains three projects: Silverlight application, Silverlight navigation application (which is the latest), and Silverlight class library

The type of website creation relies on the current ASP. NET Website

Toolbox controls are also added, including all controls contained in 2 + Silverlight toolkit package + a small number of new controls (such as errorsummary)

 

The compatibility between Silverlight 3 beta and Silverlight 2 is good. See the breaking change document below.

Ensuring that your Silverlight 2 applications work with the Silverlight 3 beta releaseintroduction

This topic discusses the changes made to the Silverlight runtime and Silverlight tools between the Microsoft Silverlight 2 and Silverlight 3 beta. the changes discussed in this article are focused on changes that might cause your older Silverlight-based applications to now fail or behave differently, not on new features/enhancements for this release.

Note corrections/additions to this document (if any) are listed here.

Contents:

· Openfiledialog. showdialog () can now only be opened from a user initiated event

· Hyperlinkbutton now navigates the entire window and not just the IFRAME that Silverlight is in

· Mouse events inside a popup now give positions relative to the pop-up not the entire application

· Readonlyobservablecollection moved from system. Windows. Controls. Data. DLL to system. Windows. dll

Openfiledialog. showdialog () can now only be opened from a user initiated event

Who is affected: all applications.

Summary

For security reasons, openfiledialog. showdialog () may only be called during a user initiated event (mouseleftbuttondown/up and keydown/UP) or derived user event Like clicking a button, checking a checkbox, etc. this brings Silverlight into line with how the other major browsers and plug-ins behave.

Hyperlinkbutton now navigates the entire window and not just the IFRAME that Silverlight is in

Who is affected: Silverlight 2 applications recompiled for Silverlight 3 beta.

Summary

In Silverlight 2, hyperlinkbutton behaved inconsistently initialize SS browsers. in Internet Explorer, hyperlinkbutton will navigate the entire browser not just the current IFRAME.

In other browsers, hyperlinkbutton navigates only the current IFRAME, which is consistent with HTML behavior. In Silverlight 3 beta, we 've changed the behavior inside Internet Explorer to match the behavior in other browsers.

Mouse events inside a popup now give positions relative to the pop-up not the entire application

Who is affected: Silverlight 2 applications recompiled for Silverlight 3 beta.

Summary

Suppose you have an element inside a pop-up that listens to mouse events:

[XAML]

<Popup>

<Border name = "border" mouseleftbuttondown = "onmouseleftbuttondown"/>

</Popup>

[C #]

Void onmouseleftbuttondown (Object sender, mousebuttoneventargs E)

{

... E. getposition (Border )...

}

In Silverlight 2, the coordinates from mousebuttoneventargs. getposition will be relative to the entire Silverlight plug-in, even though the application asked for coordinates relative to the border control (the parameter to getposition is supposed to indicate the frame of reference ). this has been fixed in Silverlight 3 beta.

Readonlyobservablecollection moved from system. Windows. Controls. Data. DLL to system. Windows. dll

Who is affected: Silverlight 2 applications recompiled for Silverlight 3 beta.

Summary

This class has been moved into system. windows. DLL so that other APIs in system. windows. dll can use it. in order to minimize download size impact we 've removed some uncommonly used methods.

Note that this will not affect applications compiled for Silverlight 2. if you use readonlyobservablecollection in Silverlight 2, your. xap file will contain a copy of system. windows. controls. data. DLL. when Silverlight 3 beta runs your. xap, it will use. xap's copy of system. windows. controls. data. DLL and that version of readonlyobservablecollection, not the version that ships in the system. windows. DLL of Silverlight 3 beta.