Share via

Automatic Update for JScript which is part Windows Script 5.7 release

  • Article

There has been some request and suggestion that when the JScript team feels that there are so many advantages of JScript update which went as part of Windows Script 5.7 release, why this is not being pushed as part of Windows Automatic Update. Well, we do agree that making the JScript DLL (which is part Windows Script 5.7 package) delivered as automatic update will indeed help us in many ways including:

  • Reaching a huge number of our customers. This being a push rather than a pull (where the user needs to go and download the package from Microsoft Download Center) will certainly help in having this installed on a large number of machines.
  •  Web site owners/developers whose site has improved will indeed want to have their customer see the same improvements. Now the chances that their customer will also go to the download link and download the package is again bit low. However doing an automatic update will help them too.

When Microsoft started the concept of automatic update, many items like a bug fix/feature request also made part of this. This lead to some system being broken. So people were generally skeptical consuming the latest updates and be broken. Instead they chose to be vulnerable.

Microsoft as a company has tried its level best to erase this perception. As a result of this only high vulnerable bug fix (security bugs) and similar items are only passed as part of auto-update. This is to make sure that we push things which are extremely of high importance from security/vulnerability point of view. So it's very difficult to push in general bug fixes through auto-update.

However all said the JScript team is looking at this as a priority and we are going to make a case for this. Stay tuned for further updates.

Thanks,

Don Raman

Comments

  • Anonymous
    September 15, 2007
    The comment has been removed

  • Anonymous
    September 30, 2007
    The comment has been removed

  • Anonymous
    September 30, 2007
    Thanks! I was thinking that the JScript engine running inside Silverlight could have better performance than the one in IE ("native") because it would use the CLR. It could get a better garbage collector for instance. And if a script running inside a Silverlight plugin can access the HTML DOM of IE, then it would be possible to run an Ajax app with CLR performances. It would be like using Rhino inside an applet and modify HTML using netscape.javascript.JSObject.

  • Anonymous
    September 30, 2007
    Yes thats correct. The JScript that ships with Silverlight 1.1 September Refresh is based on DLR and will leverage all the good things about DLR. And yes from Silverlight you can access DOM. Here is a link to good article describing this in a neat way: http://www.codeflakes.net/blog/post/Silverlight-how-to-let-the-DOM-interact-with-Silverlight.aspx Thanks, Don.

  • Anonymous
    January 19, 2008
    Yes, it would be nice to have WS 5.7 automatically installed. My heavy ajax app is almost unusable in IE6 with version 5.6 and it works very well after the upgrade.

  • Anonymous
    February 18, 2008
    is 5.7 still not available for x64 win2k3 servers?

  • Anonymous
    February 18, 2008
    Please refer to this link: http://blogs.msdn.com/jscript/archive/2007/11/29/jscript-performance-update-for-ie6-users.aspx

  • Anonymous
    August 31, 2011
    please help to fix the scipt debugging in IE8