Silverlight RC2 On The Way – We’re Getting CLose!

As we close down on the release, we're actually pushing out an update to the Silverlight RC build in the next couple of hours. The update is Sunday night's drop - build 20730 (the last release was 20724), and I'm going to informally dub it "RC2" for ease of reference.

This is one of a few critical updates that we'll be pushing down over the next couple of weeks to test the update mechanism. If you've set your update options to prompt on install, you'll see a dialog very like the following when you next visit a page that contains Silverlight functionality:

All updates will require a restart at some time to take advantage of the functionality changes. All prompted updates can be “postponed” by not restarting the process until you are ready; when you next restart the browser or open a new window, you'll see the updated version (you can right click on any Silverlight content and choose "Silverlight Configuration" to see which build is actually running).

There's no additional work required to support this release - there are zero breaking changes compared to the RC1 release, and you don't need to update your silverlight.js file or anything else for your code to work.

To be clear, we're not pushing this update out because we've found a security issue; it's more of a public test of our update broadcast system (with the added bonus that you get the latest bits installed). We'll do a few more of these on an approximately weekly basis until we release the final Silverlight 1.0 bits; from that point on we'll only update like this as necessary to fix a critical issue.

Comments (18)

  1. MSDN Archive says:

    By "requiring a restart" you mean a restart of browser, not a restart of the system, right?

  2. Anonymous says:

    "Restart" means restart the browser.


    Steve Herndon

    Silverlight Deployment

  3. Anonymous says:

    Early we install RC1, I surprise rapid release for this version

    What type of issue resolve this RC??

  4. swildermuth says:

    Any ‘breaking’ changes for RC to RC2?

  5. Tim Sneath says:

    Shawn, not a thing – or at least, if you find one, please let us know because it’s a regression bug we’ll want to fix!

  6. Tim Sneath says:

    Efren, it’s really more of a test of our servicing infrastructure. There are perhaps ten bug fixes since RC1 – an odd small memory leak or minor regression in most cases. No new features, nothing to "notice" as such.

  7. Anonymous says:

    Any chance Silverlight will support 64bit browser?  If so it would one up Flash.

  8. Anonymous says:

    Hi Tim

    Since I installed the alpha refresh of 1.1, I keep getting the install screen on several samples… Of course, when I click on it, detects that I have already installed it, so I can’t do anything.

    Will this issue be fixed? I saw users on the Silverlight forums having the same issues…


    Gill Cleeren

  9. Anonymous says:

    Silverlight 1.0のRC2が早速リリース!?

  10. xuchen0306 says:

    Hi Tim, you must be the one in MS. And I want report a bug about Silverlight.js in Silverlight 1.1 Alpha Refresh SDK.

    I think it is MS problem in Silverlight.js file now.

    It always ask you to install Silverlight 1.0 RC in a machine which is not installed Silverlight run-time, when visiting the page which is developed by Silverlight 1.1 Alpha Refresh.

    For example:

    Because when you visit sample in quick starts which is in 1.1 Alpha Refresh version in a machine which is not installed any silverlight, it also show the logo of 1.0 RC icon. You can try following link in a machine which is not installed any silverlight run-time. And even you installed 1.0 RC by clicking the icon, that icon will show again. you can try:

    BTW: I have post it in the forum, you can see (my handle is ‘xuche’ there):

    And I want a official recorrection of Silverlight.js file.

    Would you help to let your team make it and release?

    Thank you very much!

  11. Anonymous says:

    Default access: Scott Barnes highlights what I missed in the wording from Tim Sneath — it appears that the default option for auto-updates in the upcoming Microsoft Silverlight browser plugin is to silently update: to always accept new code from Microsoft

  12. Anonymous says:

    微软Silverlight的开发人员在Blog上宣布即将发布一个Silverlight的RC2版本 build 20730,时间是本周日,(目前的版本是RC 20724). 在升级时您会得到明确的通知,本次更新修正了上一个版本的Bug和安全问题,并没有对RC1的功能作出改进,并且旧版本生成的代码文件都可以不用作任何改动.

  13. Anonymous says:

    Probably not the right place to ask, but will it be possible to host the silverlight runtime so that apps we develop for an intranet will be able to install from there rather than the internet? Typically we deploy to factories where there may be no internet access but we’d like to take advantage of silverlight – particularly 1.1.


  14. Anonymous says:

    I can’t be bothered to try this out right now, but will this updating mechanism work if I install SL from Admin-priv account and then never log in as admin again and use a limited/normal user account without UAC? (eg. this standard user acc has no rights to update any Silverlight files)

    That’s a pretty important update scenario and I would say a blocking issue if it doesn’t work.

  15. Anonymous says:

    SliverLight能够 给我们带来新的体验





  16. Anonymous says:

    Tim blogs Silverlight RC2 almost with us! Also click here to see more examples built in Silverlight…

  17. Anonymous says:

    It would be wonderful if Silverlight would run in a 64-bit browser.

  18. Anonymous says:

    Where is the best place to report bugs, please?

    A couple I consider:

    * Apparent 16Kb restriction on the size of an ASX playlist

    * Documentation on what should happen re: buffering the next entry of a playlist while the current one is still playing (does that mean the MediaElement can be in a buffering-next-playing-current state, conceptually?)

    * Not accepting an ASX playlist that is output from a .NET XmlSerializer (unless I’m missing a schema; but google can’t find one…) – it fails with AG_MEDIA_UNABLE_TO_PLAY or some such if there’s an XML header or schema-attributes in the root element; nor does it accept XML comments before the root element.

    * Silverlight.createObject requiring that width and height be passed as strings, instead of accepting numbers (if numbers are passed, width and height of the object are empty, which I guess renders as 0x0 (I can’t see it to tell, y’know?  😉  )).  I guess this is so we can pass in px or %, but if neither of those are present, it would be nice if it defaulted to one or the other instead of silently being 0x0.

Skip to main content