That bug is our fault and I'm happy to say we've fixed it in Silverlight 3 so when Silverlight 4 beta sites start showing up in the wild hopefully we won't see this issue as often. One bug is that the built-in prompts from Silverlight 2 don't tell the website what version of Silverlight was required so the website can't do something intelligent. Either way, when you click to install/upgrade it just installs Silverlight 2 again because that's the latest release that is publicly available. If it specifies a minRuntimeVersion of '3.0.x.x' it might cause your currently installed Silverlight 2 runtime to prompt you to upgrade (a 'real' dialog that isn't html) or maybe they prompt you with their own web ui to install. The site requires the Silverlight 3 Beta and so it prompts you to install Silverlight or upgrade to the latest release if you don't already have Silverlight 3 installed. This has happened a handful of times with the Silverlight 3 developer preview release that was made available a few months ago. The more common variation of this category is a site that is built against a Beta or Release Candidate that isn't publicly released to end-users. If you have or find a site like this, tell the site author to either take the content down or update it to work with an officially released version of Silverlight. Installing the currently released Silverlight runtime doesn't register the Beta mime type so you just get prompted again. But, the infinite install prompt rears its ugly head when sites use the Beta mime type but link to the currently released Silverlight installer instead of the link we asked them to use.
We also told people to use a special Beta-specific installer URL so that use of the mime type wouldn't be horrible because the URL goes to a page on mscom/Silverlight that says the site you visited was built against a Beta that is no longer available.
We knew ahead of time that the Beta releases would NOT be compatible with the final Silverlight 2 so we gave them special mime types that only work for those Beta releases. On the less obvious and far more common end, I've come across a number of sites that were built to target one of the Silverlight 2 Beta releases and they specify the Beta-specific application/x-silverlight-2-b1 or application/x-silverlight-2-b2 mime types in the object tag.
0 kommentar(er)
