×

First time here?

You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting!

Small public service announcement here for Silverlight developers…we released a minor update to the runtime and SDK today.  You may see this referred to as Silverlight 3 GDR2.  Formally it is version 3.0.40818.0.  Usually when a release pops up people are curious about what is in it and why there wasn’t some major announcement.

NOTE: “GDR” is Microsoft-speak for general distribution release.

If you are interested in the full release history for Silverlight it is always available online (click the deployment section).  This latest minor release really had several updates for improving some media and network scenarios, but namely the main driver on this release was GB18030, which is a Chinese government standard for support of its national characters.  The standard reads:

“All products currently sold or to be sold in China must plan the code page migration to support GB18030 without exception. GB18030 is a "mandatory standard" and the Chinese government regulates the certification process to reinforce GB18030 deployment.” source: http://gb18030.org

So yeah, we needed to do this :-).  Silverlight made necessary changes to ensure that Blend and Visual Studio would be in compliance.

How will this affect my users?

Most likely it won’t unless you know about the fixes and have been a customer of one of the needs.  The driver for your customers/end-users of your applications is the minRuntimeVersion attribute of the plugin.  This is what tells the plugin on the end user machine what version they must have at a minimum to support your application.  Unless you change this to 3.0.40818.0 then your app isn’t likely to be affected.

If you need the update to comply with GB18030 deployments for example, then you’d want to modify the minRuntimeVersion to suit your needs.  This would prompt users with an older version to install the update.  You can make this a better experience for them by following the guidance in the Silverlight Installation Experience whitepaper (you can see a very simple implementation of this here).

What about my development environment?

For your development environment, you’ll need to upgrade to the latest development runtime.  If you try to install the end-user runtime on a developer machine, you will not be successful.  This is like trying to upgrade your turbo car engine with the standard V8.  The developer runtime is a superset so you can only upgrade to another developer runtime.

The links available at the Silverlight Community Site in the Get Started section are still valid (see developer runtime links at the bottom of that page for Windows and Mac).  There are no new Silverlight Tools update you need to install at this time.  There were some minor updates to the SDK which aren’t required, but again, if you want the latest, you can always get it.

That is all.  This is not a major update, but if you’re like me and can’t stand having anything but the latest, you can go out and get it.  Note that all your current installer links for your end users will remain to work always.  We update our installation handlers on our sites each release to be appropriate.

These updates went live approximately 10:00AM PST.  There may be some still propagating across the giant tubes of the interwebs.

Hope this helps!


This work is licensed under a Creative Commons Attribution By license.



DISCLAIMER:

The opinions/content expressed on this blog are provided "ASIS" with no warranties and are my own personal opinions/content (unless otherwise noted) and do not represent my employer's view in any way.