Feedback Req: Do you need to know the list of released runtime build numbers?


Hi All,

I’ve noticed a few occasions where developers have wanted to know what Version of Silverlight is installed on the end users computer when they arrive at a site. There are a number of ways you can approach that question that will yield a response, namely in non-IE browsers tapping into the navigator.plugins["Silverlight Plug-In"].description will provide such an answer. In MSIE you realistically need to keep testing the Silverlight.isInstalled(buildnumber) until you get a FALSE (which infers the last known TRUE will yield you your known versions of installed Silverlight).

Now typically with all future builds we classify the number as being "0major.0.4monthday" (e.g. 03.0.41009) the build was released. Now this is helpful, as you can essentially run some for-loops over the month/days to yield the "Silverlight.isInstalled()" but that does often create a lot of redundancy in terms of logic.

Instead, what I’m thinking of providing is a JSON API on microsoft.com/silverlight which will provide a complete and up to date Array of Silverlight RELEASED buildnumbers that we actively support.

Is this something that folks would like or have a need for? Please reply with answers to the below questions

Questions:

  1. Why do you need this JSON Array to exist? can you expand on how you intend to use it?

  2. What else would you like to be added to this array ? (i.e. known browser/platform supported versions?)

  3. How have you found the overall "Get Silverlight" experience in terms of getting users to begin the installation (i.e. not the install wizard itself, but everything prior to this)

  4. What else would like from the Silverlight Team to help you solicit end users to Install Silverlight. Is there a blind spot we have and what would you like us to do (give it a priority weighting as well please).

Please Respond to these questions here:

http://forums.silverlight.net/forums/p/127881/286548.aspx#286548

Or

Via the Comments below.

Comments (1)

  1. ross jempson says:

    I’ve coded my own version of this, however a shared ‘library’ would have been useful at the time.

    I use my version to log to our analytics service  the % users with / without the plugin and which version.  This is very useful for analysis of adoption / penetration into the site.  And the impact SL is having on penetration.

    Funnily enough, today I am coding up our ‘Get Silverlight’ screen for those who don’t have it installed.  My feedback is that it is a little cumbersome handling the different states, e.g after install, IE needs the user to refresh, Firefox needs a restart, IE needs a restart if an older version was installed, we need a special UI for those users that don’t have a compatible browser / OS……..

    I think testing it is going to be the real pain point.  In an ideal world I am going to need a test environment with Mac, Linux, Windows, multiplied by various browsers, multiplied by the combination of previous Silverlight versions (1, beta 2, 2, beta 3, 3).

    For example, where can I even get the old Silverlight plugin installers so that I can setup such a test environment?

    I have played with Expression Web 3 superpreview, which is useful to see the initial ‘You don’t have Silverlight’ UI in various browsers, but I can’t actually install the plugin and walk through the rest of the process.  And ideally I would need to install old versions of the plugin, then test the site.