Silverlight 4 February 2011 Update Released Today

Today (at approximately 10:00 AM PST) our team released an update to the Silverlight 4 runtime.  This update, dubbed internally as “GDR3,” provides an update in the following key areas (KB2495644):

• Timestamp issues with media playback and VC-1 codec
• Visual Studio IDE crash when profiling a Silverlight application which has a pixel shader
• Enabling Silverlight to run as a 32-bit process in 64-bit Firefox on OSX
• DRM fixes for a “6207” error when playing protected content after upgrading to a version of Silverlight
• Memory leak fixes with regard to the use of in-line DataTemplate
• Out-of-browser applications failing to update if the application name was changed
• Media playback error when the media streams have redirect information
• Improving network latency (KB2505882)

Many readers of this blog will likely zero in on the memory leak fix here.  The issue is discussed/debated/ridiculed ad nauseam on the forums relating to this issue.  If your customer applications are facing this issue and you chose not to apply one of the two workarounds, then you want to encourage your customers to upgrade to this release.  This can be done using the minimum runtime version attributes in your <object> tags where you use Silverlight.  This will prompt the user for an upgrade.  Of course, I’ve stated my opinion many times before that this should be a customized experience and we’ve even provided sample code to do so in our installation experience whitepaper.

‘I noticed <your-favorite-bug/feature> isn’t fixed here’
Each service release doesn’t fix our backlog completely.  If there is an issue you are seeing with Silverlight after applying this update, please, please, please log a bug on the product.

Read more: Method ~ of ~ failed

Read more: Silverlight Runtime

Posted via email from Jasper-net