×

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!

Yesterday a minor update to the Silverlight 2 runtime was released.  You may see terms of “GDR 1” floating around.  That’s pretty much an internal term at Microsoft referred to as “general distribution release” – yeah, I know we have a lot of random terms.  Think of it just as an incremental update.  If you are curious for Silverlight’s entire release history, you can view that here.

So what’s in it?  Well, nothing earth shattering if you were expecting feature updates.  There were some needed fixes based on customer feedback that we included in this update (which is version 2.0.40115.0).  Basically I would bucket it into a simple list for you:

  • Various accessibility fixes relating to UIAutomation
  • Fixes for certain anti-virus vendors scanning algorithms
  • Much needed fix for OSX platform when users modify their font locations (i.e., people with font management tools usually)
  • Bug in IsolatedStorage quota increasing when the user’s display language is set to one that Silverlight has not been localized to

That’s about it…no new controls, nothing suddenly going to make you amazed and shocked.  But it was a needed release to fix these issues. 

So what should you do?  Depends. 

If you are a consumer…

You really shouldn’t need to do anything unless you are specifically experiencing one of the issues above.  Web developers using Silverlight and needing their user’s to have this update will update their site and let you know.  There isn’t a huge need to rush out as an end-user and download the update.  Besides, if you have it configured to automatically update, then in due time you’ll get the update through that mechanism and won’t have to do anything.  If you absolutely want to be on top of things, then feel free to grab the latest updated runtime by visiting the download link.

If you are a developer…

If you are directly affected by the changes above then you should update your application.  There are really two things you need to do:

For the latter note this is a simple change.  Update your “MinRuntimeVersion” attribute in your hosting page/content to ensure that end users have the latest runtime version for your application.  Again, you should only really need/want to do this proactively if you (or your users) are directly affected by the updates in this release!  Here’s how you’d do it.

NOTE: Even though you update the developer runtime the Visual Studio project templates are not updated to set the default runtime version to the updated version so each new Silverlight project using those templates will still reference minRuntimeVersion=”2.0.31005.0” – if you want to change that you can modify the template.

UPDATE: How to modify the default value of the template

I’ve received some errors myself after changing this, so while it sounded like a good idea :-), I can’t recommend altering this reg value to the updated version – if I find out why, I’ll post here.

I got some questions about exactly how you would get the default web templates to change the generated test pages to emit the updated version number.  Since these are pages in a web project and not the Silverlight project, it isn’t easily found.  In fact, that value gets pulled from a registry setting.  The setting is at (removing the Wow6432Node if you are not on 64-bit Windows):

   1: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Silverlight\v2.0\ReferenceAssemblies]
   2: "SLRuntimeInstallVersion"="2.0.40115.0"

and you need to change the value to match what you want that to be.  Again, this is not a required step at all.

As a reminder, messing with your registry can be dangerous if you have no idea what you are doing.  Backup your reg keys, don’t blame me if something goes wrong :-).

If you are using the ASP.NET Silverlight control you’d modify the MinimumVersion and AutoUpgrade attributes:

   1: <asp:Silverlight ID="Xaml1" AutoUpgrade="true" runat="server" 
   2:                 Source="~/ClientBin/SilverlightApplication3.xap" 
   3:                 MinimumVersion="2.0.40115.0" Width="100%" Height="100%" />

If you are using the <object> tag instantiation you’d modify the minRuntimeVersion and autoUpgrade attributes in the <object> tag for your Silverlight application:

   1: <param name="minRuntimeVersion" value="2.0.40115.0" />
   2: <param name="autoUpgrade" value="true" />

If you are using Silverlight.js to create the object you’d modify the version attribute when passing it in to the properties parameter of the createObject function (sample):

   1: Silverlight.createObject(
   2:             "ClientBin/SilverlightApplication1.xap",  // source
   3:             silverlightControlHost,  // parent element
   4:             "slPlugin",  // id for generated object element
   5:             {
   6:                 width: "100%", height: "100%", background: "white", 
   7:                 version:"2.0.40115.0"
   8:             },
   9:             { onError: onSLError, onLoad: onSLLoad },
  10:             "param1=value1,param2=value2", 
  11:             "context"    // context helper for onLoad handler.
  12:         );

That’s it!  Hope this helps.  The team is diligently working on Silverlight 3!


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


2/19/2009 11:29 AM | # re: Silverlight 2 gets minor update
Tim: As always, great post (and great blog in general), much appreciated. Curious, on the 'minRuntimeVersion' param, is there a reason to always be updating our sites with the latest full release number as opposed to just specifying '2.0'? Can get tedious... Thx.
2/19/2009 11:49 AM | # re: Silverlight 2 gets minor update
Malcolm -- good point/question! One reason is that beta builds also had the "2.0" major/minor versioning scheme but are no longer supported. In theory it *shouldn't* be, but to be safe you could target exactly what you built off of. I would say at worst the minimum should be 2.0.31005 which represents the initial SL2 release. Obviously if you move an application to Silverlight 3 you'd want to change the min runtime requirement for that version.
2/19/2009 12:16 PM | # re: Silverlight 2 gets minor update
I was looking at this release history document

download.microsoft.com/.../...lease%20History.html

It says this update includes

UI automation stability fixes, including:
graceful failures when attempting to use features that require .Net Framework 3.0 or 3.5 on machines that do not have either framework installed

What functions in silverlight require the .net framework 3.0 or 3.5 to be installed?
2/19/2009 2:21 PM | # re: Silverlight 2 gets minor update
Thanks for the clarifications Tim
2/19/2009 4:27 PM | # re: Silverlight 2 gets minor update
Hey Tim,

Off-Topic Query, what kind of Blog ENgine you use? Is it opensource?

Thanks,

Mudassir Azeemi
San Francisco, CA
2/19/2009 4:30 PM | # re: Silverlight 2 gets minor update
Hi Mudassir: timheuer.com/.../...oolbox-tools-for-blogging.aspx details on what I use.
2/19/2009 6:20 PM | # re: Silverlight 2 gets minor update
Tim does this fix the gray screencast bug?
http://silverlight.net/forums/t/6019.aspx
2/19/2009 6:23 PM | # re: Silverlight 2 gets minor update
Michael -- no it does not :-(
2/20/2009 12:52 AM | # re: Silverlight 2 gets minor update
Hi Tim,
I have just installed the SDK for visual studio, the install finessed successfully but when starting visual studio I do not see the option to create a Silverlight project.
Do you have any hint for me?
2/20/2009 7:42 AM | # re: Silverlight 2 gets minor update
Hi Tim

Does this release include fix on "Popup MouseLeave"-event not firing bug?
Its also mentioned here:
http://silverlight.net/forums/t/16073.aspx
2/20/2009 8:29 AM | # re: Silverlight 2 gets minor update
Adnan - I don't believe it does.
2/20/2009 8:34 AM | # re: Silverlight 2 gets minor update
Peter -- did you install just the SDK or the actual VS Tools? Make sure you install http://go.microsoft.com/fwlink/?LinkId=129043 for the full VS tools (dev runtime, sdk and VS projects)
2/20/2009 12:20 PM | # re: Silverlight 2 gets minor update
Aaawww no fixes for the PNG transparency issues? Too bad.
2/20/2009 12:53 PM | # re: Silverlight 2 gets minor update
Hi Tim - thanks for the post. Like Ken Tucker I was curious about the "UI automation stability fixes, including: graceful failures when attempting to use features that require .Net Framework 3.0 or 3.5 on machines that do not have either framework installed" comment.

I was under the impression that Silverlight was oblivious to an .NET installation on the client machine.
2/21/2009 6:45 AM | # re: Silverlight 2 gets minor update
Guy,

I found this on Tim Sneath's Blog

apologies - we could probably be clearer here on what this means. Essentially, this was a bug that could be triggered in certain situations where you were using the accessibility tools (e.g. magnifier) on Silverlight content on a machine without .NET Framework installed. In short, the bug was an accidental dependency that has now been removed.
3/2/2009 10:34 AM | # re: Silverlight 2 gets minor update
Hey Tim,

Off-Topic Query, is it possible load an external dll to run on a current web aplication? Thanks in advance.
3/2/2009 1:56 PM | # re: Silverlight 2 gets minor update
Mariana -- if what you mean is if you can load a third party dll in a Silverlight application, then yes -- as long as it is a Silverlight-capable dll :-) -- you can't just load any .NET dll.
3/11/2009 11:30 AM | # re: Silverlight 2 gets minor update
Were any performance updates made? I figure that I spend about two hours per day waiting for Visual Studio...
3/11/2009 11:35 AM | # re: Silverlight 2 gets minor update
Hi Cleon26, this was an update to Silverlight runtime, not tools...unrelated to Visual Studio.
3/12/2009 8:08 AM | # re: Silverlight 2 gets minor update
Thanks Tim. I was secretly hoping that all the rendering/compiling that Visual Studio seems to do was somehow making use of this underneath.
5/20/2009 4:40 AM | # re: Silverlight 2 gets minor update
Great sharing..
it look like silverligt have many features now..
that good..
8/12/2009 12:49 PM | # re: Silverlight 2 gets minor update
thanks Tim, for the clarification..
1/13/2010 11:31 AM | # re: Silverlight 2 gets minor update
Thanks Tim for adding more features. :)
1/13/2010 12:11 PM | # re: Silverlight 2 gets minor update
Great help!
I´ll certainly implement them in my next projects.
Thanks a lot!
1/29/2010 6:16 PM | # re: Silverlight 2 gets minor update
Great sharing..
it look like silverligt have many features now..
that good..
10/30/2013 6:23 AM | # re: Silverlight 2 gets minor update
Thank you for the great quote. I just wish higher education wasn’t so expensive these days.
10/31/2013 10:06 AM | # re: Silverlight 2 gets minor update
Hello Dear, Really your blog is very interesting.... it contains great and unique information. I enjoyed to visiting your blog.

 
Please add 4 and 3 and type the answer here:

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.