I was confused (maybe you will be also) when I installed the SL2RTW bits this morning (2008-Oct-14), because they are binary identical to the bits I had installed two days ago on 2008-Oct-12. The 31005.0 version number is also the same.
See the files in this directory:
C:\Program Files\Microsoft Silverlight\2.0.31005.0
Here are the main ones (notice those build dates are 10 days ago):
10/04/2008 09:48 PM 289,616 System.Core.dll
10/04/2008 09:48 PM 162,632 System.Net.dll
10/05/2008 02:16 AM 143,184 agcore.debug.dll
10/04/2008 09:48 PM 3,085,632 agcore.dll
10/04/2008 09:48 PM 3,076,424 coreclr.dll
10/04/2008 09:48 PM 1,461,064 mscorlib.dll
10/04/2008 09:48 PM 11,080 mscorrc.dll
10/04/2008 09:48 PM 783,168 npctrl.dll
10/05/2008 02:16 AM 495,424 sos.dll
10/04/2008 09:48 PM 236,352 system.dll
"The final build number is 31005.0; some of you may already have installed this build without knowing it – we quietly updated the RC build on silverlight.net through the last couple of weeks to the latest builds, and the version we released a week ago was the
one that was declared RTW."
Yep, we have been updating the developer runtime so that developers would have RTW (or near RTW) bits ASAP. The final build was actually created on 10/05 (hence the 1005 in the build number) - and once tested, released to developers.
But the consumer runtime was not published until today.
------------------------------------
If this post has solved your problem, please select ‘Mark as answer’
Program Manager | Silverlight Tools for Visual Studio | Microsoft Visual Web Developer | www.dullard.net
Alan Cobb
Member
479 Points
208 Posts
Final SL2RTW build actually "stealthily" released a week ago!
Oct 14, 2008 06:49 PM | LINK
I was confused (maybe you will be also) when I installed the SL2RTW bits this morning (2008-Oct-14), because they are binary identical to the bits I had installed two days ago on 2008-Oct-12. The 31005.0 version number is also the same.
See the files in this directory:
C:\Program Files\Microsoft Silverlight\2.0.31005.0
Here are the main ones (notice those build dates are 10 days ago):
10/04/2008 09:48 PM 289,616 System.Core.dll
10/04/2008 09:48 PM 162,632 System.Net.dll
10/05/2008 02:16 AM 143,184 agcore.debug.dll
10/04/2008 09:48 PM 3,085,632 agcore.dll
10/04/2008 09:48 PM 3,076,424 coreclr.dll
10/04/2008 09:48 PM 1,461,064 mscorlib.dll
10/04/2008 09:48 PM 11,080 mscorrc.dll
10/04/2008 09:48 PM 783,168 npctrl.dll
10/05/2008 02:16 AM 495,424 sos.dll
10/04/2008 09:48 PM 236,352 system.dll
A web search for "Silverlight 31005.0" eventually turned up the explanation on Tim Sneath's blog:
http://blogs.msdn.com/tims/archive/2008/10/13/silverlight-2-today-is-the-day.aspx
"The final build number is 31005.0; some of you may already have installed this build without knowing it – we quietly updated the RC build on silverlight.net through the last couple of weeks to the latest builds, and the version we released a week ago was the one that was declared RTW."
Alan Cobb
www.alancobb.com/blog (Silverlight blog)
amyd
Member
722 Points
124 Posts
Re: Final SL2RTW build actually "stealthily" released a week ago!
Oct 14, 2008 07:02 PM | LINK
Yep, we have been updating the developer runtime so that developers would have RTW (or near RTW) bits ASAP. The final build was actually created on 10/05 (hence the 1005 in the build number) - and once tested, released to developers.
But the consumer runtime was not published until today.
If this post has solved your problem, please select ‘Mark as answer’
Program Manager | Silverlight Tools for Visual Studio | Microsoft Visual Web Developer | www.dullard.net
preishuber
Contributor
3572 Points
658 Posts
Re: Final SL2RTW build actually "stealthily" released a week ago!
Oct 14, 2008 07:08 PM | LINK
yes that's true. The bits were finished last week. But it take some time to bring it all together ( Blend, Tools) and make short integration tests.
http://www.ppedv.de
Alan Cobb
Member
479 Points
208 Posts
Re: Final SL2RTW build actually "stealthily" released a week ago!
Oct 14, 2008 07:32 PM | LINK
Hi Amy and Hannes,
OK, thanks for the additional details (like where the "1005" came from in the "2.0.31005.0" build number).
I guess there is no way to know ahead of time whether a "release candidate" will be chosen as "The One" (U.S. election joke, sorry).
Alan Cobb
www.alancobb.com/blog (Silverlight blog)