Silverlight v1.1 is now Silverlight 2.0, it makes sense marketing-wise but the attempted reasoning leaves a bitter taste.
As covered earlier this week, even Microsoft were confused by their own versioning for Vista — and the news is that they are at their old naming tricks again.
At the time Silverlight was launched, it came in an inital 1.0 beta version but there was also a v1.1 in the works. Now because of the sheer gigantic implications of the feature set in Silverlight v1.1, it demands that it be named Silverlight 2.0 as it is simply too much of an improvement for a point release.
According to Microsoft the features that have caused this rebranding are: UI Controls, Networking support, a subset of the WPF Framework, .NET Base class support (examples are LINQ and DOM integration). The last two are decent enough features, but the first two should be a given, one would think.
To me it really does sound like someone in marketing worked out that it would actually make more sense to call it 2.0 than 1.1. For once Microsoft's branding is making more sense — just don't try to justify it with features.
If you would like to read the original announcement without my sardonic commentary, go to Scott Guthrie's blog. Guthrie also details some ASP.NET and IIS7 improvements in the post.