Silverlight 4 service release (September 2010)| Comments
- | Posted in
Today we released an update to Silverlight 4 (update build is 4.0.50826.0) along with an updated SDK. We appreciate our customers’ patience on working with us to help identify and verify necessary updates to this service release. You can find all the details in KB2164913. Here are the relevant highlights:
- SDK feature to enable Add New Row capabilities in DataGrid control
- Improving startup performance of Silverlight applications
- Adding mouse wheel support for out-of-browser applications on the Mac platform
- Various media-related fixes around DRM content
- Fixed memory leak when MouseCapture is used
- Fixed memory leak for DataTemplate usage
All the installer links have been updated to leverage these new bits for our customers.
For end users
For end users, having them simply install the runtime will provide them with the updated bits and benefits of the fixes/features in this service release. The best way to
force encourage your users to upgrade to this service release would be to leverage the MinRuntimeVersion attribute of your object tag:
1: <object data="data:application/x-silverlight-2," type="application/x-silverlight-2"
2: width="640" height="400">
3: <param name="source" value="YOUR_PATH_TO_XAP" />
4: <param name="background" value="white" />
5: <param name="minRuntimeVersion" value="4.0.50826.0" />
6: <param name="autoUpgrade" value="true" />
7: <a href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50826.0" style="text-decoration: none">
8: <img src="http://go.microsoft.com/fwlink/?LinkId=161376" alt="Get Microsoft Silverlight"
9: style="border-style: none" />
Notice lines 5 and 6 above. This would trigger that the end user is required for your application to run and require them to upgrade. The minRuntimeVersion/autoUpgrade are the minimum to require your user to upgrade to the later version. Ideally you would follow good installation experience guidance (see “Installation Experience Whitepaper” with complete sample source code) to customize your install and/or upgrade experience.
If you are a developer and authoring Silverlight applications you may want to grab the new developer bits and updated SDK:
I would install the developer build first and then the SDK and you’ll have a refreshed environment. As with any release we try to get you the information as soon as possible and sometimes the information flows faster than the download servers replicate. If you aren’t getting the updated bits using the links above, please be patient as the download servers from Microsoft refresh their replication caches.
Note that when you now create a new project you’ll be using the new SDK and so the minRuntimeVersion (see above) of the project templates as well as compiled bits for your SL4 application will be using/requiring the updated runtime.
There are NO Visual Studio tools updates for this release so the Silverlight4_Tools.exe package is not needed to re-install.
For Visual Studio LightSwitch Users
When Visual Studio LightSwitch shipped they included a pre-release later build of Silverlight 4. This caused some issues for customers who were using a single machine to evaluate LightSwitch but also using the same machine. Any Silverlight 4 application developed and deployed would give customers messages indicating that they needed a later version of Silverlight, but were unable to acquire a compatible version!
This is now solved with this service release. Simply put: If you are using LightSwitch, install the updated developer runtime and SDK. This will solve this issue and allow you to develop LightSwitch applications as well as production Silverlight 4 applications.
Hope this helps! As always if you have feedback on Silverlight, here are some methods of providing feedback to our team.
Please enjoy some of these other recent posts...