- 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. Don’t assume someone else has. There is a specific way you can log a product bug on Silverlight as I’ve outlined in this post: Ways to give feedback on Silverlight. The ideal bug is one that is detailed, reproducible, and provides an actual repro project/sample. This is the fastest route to getting a bug understood and evaluated.
Getting the update
As with all service updates, this update will be made available to customers via Microsoft Update. If you are a developer and don’t want to wait, you can download the bits here (please be aware network propagation across the globe might take a few hours):
There is NO SDK update for this release. As a developer you only need to update the developer runtime on your machine to continue enabling Silverlight development but to also have the new runtime on your machine as a user as well. Please note that by you, the developer, simply having the updated dev runtime doesn’t “force” your apps to use it. This is controlled by using the minRuntimeVersion flags in your <object> tag to trigger what the minimum requirement is for your application.
Hope this helps!
Please enjoy some of these other recent posts...