Silverlight 1.0 RC1 is Here!

Silverlight 1.0 RC1 is Here!

  • Comments 77

As indicated in a previous post, we're homing in on the launch of Silverlight 1.0, and today marks another milestone with the launch of the first release candidate. Since the beta we released at MIX, we've fixed approximately 2000 bugs and work items and we're now feature complete with the final JavaScript-based API. This version of the runtime is vastly more stable than the beta release: our stress test runs show improvements of two or three orders of magnitude in many cases, and the product demonstrates the polish one might expect from a near-final release.

Along with the 1.0 RC1 release, we've also refreshed the 1.1 bits. We've not exposed any significant changes in the .NET extensions, but the 1.1 "alpha refresh" includes the same core runtime as 1.0 RC1. A note on installation: if you have the beta release on your machine, there's no need to uninstall - simply run the RC1 installer and it will overwrite the existing binaries on your machine.

Here's the runtime itself:

Some tools for building Silverlight applications:

Inevitably (given that this release isn't 100% compatible with the previous one, particularly as regards the object activation model), a lot of the samples out there today are broken. We've worked with a few folk that we know to help them prepare for this release, but if you have a Silverlight sample or site out there today based on the existing beta release, you'll want to pick up the new silverlight.js and work through the breaking changes to move your site up to the new release. We won't break you again, we promise!

  • Tim Sneath blogged this a few minutes ago: http://blogs.msdn.com/tims/archive/2007/07/27/silverlight

  • where is the RC then...?? it's not on the download site...

  • Along with the 1.0 RC1 release, we've also refreshed the 1.1 bits. We've not exposed any significant

  • As indicated in a previous post , we're homing in on the launch of Silverlight 1.0, and today marks another

  • Vu sur le blog de Tim Sneath : As indicated in a previous post , we're homing in on the launch of Silverlight

  • Congratulations mate and send my thanks to the rest of the silverlight team on such a great product. It is definetely living up to my expectations, actually far exceeding it.

    Looking for better things to come from you guys in the future...

    LiquidBoy

  • Tim Sneath からです。 Silverlight 1.0 RC1 is Here! 表題通り最新版の Silverlight リリースがアナウンスされています。 1.0に関して言うと ベータ から見て約2000個もバグが無くなった事。

  • zyborg: microsoft.com is a huge site and it takes a while for all the bits to propagate to all the servers.   Technically it's available but you might not be able to actually see it for a few hours.

  • Details here .

  • Tim Sneath has two exciting posts up on his blog: Silverlight 1.0 RC 1 Is Here What's New In WPF 3.5?

  • The download URL is not working for me...

  • Hey,

    I got a few questions about the versioning scheme of SilverLight 1.1 in the assemblies. Hopefully you'll be able to answer or to point me to someone :)

    In the first Alpha of SilverLight, the assemblies where versionned as 2.1.xxxx, now it's 1.1.xxx. That's ok, but in the assemblies, the version string of the metadata is still 2.0.50727, which is the version number of the .net 2 framework, so it's somewhat confusing for tools dealing with assemblies. Do you plan to change that? Also, it looks like you incremented the CLI header version from 2.0 to 2.5. Do you plan any metadata layout change, or is it only for the sake of being able to distinguish SilverLight assemblies to normal assemblies? That would really help to have something consistent inside the metadata.

    Many thanks,

  • zyborg, you might try the "direct link" hyperlink next to the Silverlight runtime entries, rather than the indirect links to the pages themselves; as mentioned, it will take a couple of hours to propagate through the download center but the direct link should work in the meantime.

  • Silverlight Cream for July 27, 2007

  • To add just another thing to my comment, it appears that the CLI header version has not been incremented, so my concern is mainly about the string version, that could be used to determine which version of the runtime this assembly is supposed to work on. It should really be something else that the version number of .net 2.0.

Page 1 of 6 (77 items) 12345»