Download details: Windows Script 5.7 for Windows 2000
<http://www.microsoft.com/downloads/details.aspx?familyid=c03d3e49-b40e-4ca1-a0c7-cc135ec4d2be&displaylang=en&tm>
Download details: Windows Script 5.7 for Windows XP
<http://www.microsoft.com/downloads/details.aspx?familyid=47809025-d896-482e-a0d6-524e7e844d81&displaylang=en&tm>
Download details: Windows Script 5.7 for Windows Server 2003
<http://www.microsoft.com/downloads/details.aspx?familyid=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4&displaylang=en&tm>
--
Michael Harris
MVP - Admin Frameworks
No new features that I know of - the most likely upgrade advantage is in not
publicly disclosed bug fixes and security holes patched.
At least now the WSH version available for older Windows OS versions are
more in sync with the WSH version included with Vista.
Thanks for the info and link. :)
Good Luck, Ayush.
--
Scripting Solutions Center : http://snipurl.com/Scripting_Solutions
"Michael Harris (MVP)" <mikhar.at.mvps.dot.org> wrote in message
news:%23WTMS7v...@TK2MSFTNGP05.phx.gbl...
Assuming you mean as a Windows automatic update, I seriously doubt it.
Do you know if there are any plans at MS to ever fix the .toFixed bug
that has been in JScript since it's inception?
--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
So you are forgiven.
Simply post it (the bug), you were saying.
It would be likely unlikely that the function had
not emerged as defunctive before
5.7 only ?
Hic Rhodus, hic salta. = Greek.
Translated :
Proof it.
You knew where to post, but forgot the line or the word.
"Randy Webb" <HikksNo...@aol.com> wrote in message
news:-6CdnWWRkI5...@giganews.com...
Not that I'm aware of, but then I'm not exactly privy to their plans :-)...
I wouldn't even be sure that MS is privy to their plans at times :-)
Furthermore i've been "swayed" to write in powershell ... :-)
"Michael Harris (MVP)" <mikhar.at.mvps.dot.org> wrote in message
news:etuv5Fv2...@TK2MSFTNGP02.phx.gbl...
Let's try and convince Eric Lippert (http://blogs.msdn.com/ericlippert/) to
blog about what's new, if anything, in WSH 5.7. I think he's one of the
original developers, or at least he's blogged a lot about WSH internals in
the past.
Cheers,
Jason
------------------------------------------------------
PowerShell Training at SANS Conferences
http://www.WindowsPowerShellTraining.com
------------------------------------------------------
Eric moved to the C# compiler team a couple of years ago...
I did find out that the only new feature is a VBScript GetUILanguage
function.
uilang = GetUILanguage()
wscript.echo "uilang:", uilang
'output...
'
'uilang: 1033
What's odd is that snooping VBScrip.dll embedded typelib info with an object
browser doesn't reveal that the GetUILanguage function was added...
To paraphrase my Microsoft source...
The real purpose in 5.7 versions (for WSH et.al.) for pre-Vista platforms
was an internal Miscrosoft move to a common OS component binary code base
(and consistent major.minor.build numbers) across supported Windows OS
versions. WSH for Win2000/XP/2003 are now synced up with Vista as the
latest OS version.
Separate OS specific install packages still exist due to different SFP
(System File Protection) requirements for OS component installs.
That doesn't explain why 5.6 and previous versions were removed - that means
that when debugging a possible corrupt installation of Windows Script, we
now have to choose between leaving the installation entirely as it is, or
upgrading to a different version, with possibly different behaviours.
Alun.
~~~~
I agree with you 100% but unfortunately can't offer any explanation (yet)...
Resembles a shaped statement out of the ado book.
msdatashape or so.
--------------
Again here multiposted. Answering. Sorry
-------------------------------------------------
Jason. you are a little late
explaining plumes over apples
making a meal.
"Jason" <nos...@nospam.com> wrote in message
news:eZisLuZ4...@TK2MSFTNGP03.phx.gbl...
I'm still wondering why come out with WSH 5.7 when they're pushing
PowerShell.
Per one of my earlier replies on this thread...
<quote>
To paraphrase my Microsoft source...
The real purpose in 5.7 versions (for WSH et.al.) for pre-Vista platforms
was an internal Miscrosoft move to a common OS component binary code base
(and consistent major.minor.build numbers) across supported Windows OS
versions. WSH for Win2000/XP/2003 are now synced up with Vista as the
latest OS version.
Separate OS specific install packages still exist due to different SFP
(System File Protection) requirements for OS component installs.
</quote>
--
Michael Harris
MVP - Windows Server Admin Frameworks
= a misery
= miscellaneous
we listen.
"Michael Harris (MVP)" <mikhar.at.mvps.dot.org> wrote in message
news:e5FX9bq5...@TK2MSFTNGP03.phx.gbl...
thanks for the information and links. Unfortunately I can't find a w2k3 x64
version and the x32 installation exe does not work on x64 :-(
Regards
Carsten