14 DAY TRIAL // Microsoft has updated its rival to Adobe Flash this week, and is now offering Silverlight 4.0.60531.0 to users. While Silverlight 5 is in the making, with a Beta already offered to early adopters for testing, version 4 continues to be THE release for end users, which need to make the jump to 4.0.60531.0.
Customers leveraging Silverlight are bound to already know that the Redmond company has made somewhat of a tradition of updating the technology from time to time, although there’s no clearly defined refresh cycle.
Already available through Microsoft Update, Silverlight 4 general distribution release version 4.0.60531.0 can also be downloaded and installed manually.
“If you have an earlier version of Silverlight installed on your computer, this update will be offered as "Update for Microsoft Silverlight (KB 2512827)," Microsoft informed.
“This update offers a new build (version 4.0.60531.0) that is an upgrade to earlier versions of Silverlight. This update is included in current Silverlight installers.”
Build 4.0.60531.0 is designed to resolve a number of problems which impact users of previous releases of Silverlight 4, according to the software giant.
There are no less than five glitches that Silverlight 4 4.0.60531.0 is designed to resolve, with Microsoft offering all the juicy details:
“Issue 1 - MS11-039: Vulnerability in the .NET Framework and in Microsoft Silverlight could allow remote code execution: June 14, 2011
Issue 2 - You cannot use the keyboard to press a Silverlight button in Apple OS X 10.6 or in Firefox 4.0.
Issue 3 - Consider the following scenario: you have a computer that is connected to multiple monitors; you open a Silverlight page by using Firefox 4.0; you move the page to another monitor; you try to view the page in full-screen mode. In this scenario, the page is displayed in full-screen mode on the previous monitor.
Issue 4 - Consider the following scenario:
You have Windows Internet Explorer 8 together with Silverlight 4 GDR 1 or a later version of Silverlight installed on a computer.
You run a Silverlight 4 GDR 1 application that contains a custom binding on the computer. The binding has a polling duplex binding element that uses a MultipleMessagesPerPoll value. This value is used during duplex communication. The HTTP stack is set to use the BrowserHttpWebRequest object.
A poll reaches the ServerPollTimeout value and times out, and no operation originates from the client-side. In this scenario, an error occurs.
Issue 5 - Assume that a Silverlight 4-based application has a DependencyObject object that is set from a StaticResource markup extension. The markup extension is in a template. When you run the application, a memory leak occurs in the template.
Feature that is added by this update - An InjectClientInformation property is added to the LicenseAcquirer class of the System.Windows.Media namespace.”
Silverlight 4 4.0.60531.0 is available for download here.