MicrosoftAll this talk of sunsetting VBScript: "Technology has advanced over the years, giving rise to more powerful and versatile scripting languages such as JavaScript". I would just like to point out that as of the January 2025 build of Windows Server 2025 (OS build 26100.2894), JavaScript in Classic ASP doesn't work. It's fine until you try to instantiate any objects, e.g.
<% var objFSO = new ActiveXObject("Scripting.FileSystemObject"); %>
causes the page to throw an error 500 and writes an Active Server Page to the Application Event Log:
Script Engine Exception. A ScriptEngine threw exception 'C0000005' in 'IActiveScript::SetScriptState()' from 'CActiveScriptEngine::ReuseEngine()'
Yet the equivalent VBScript works fine (as long as you've not disabled the feature). So we can't even migrate all our Classic ASP code from VBScript to JScript server-side.
Would Naveen_Shankar one day provide a meaningful answer to SERVER-SIDE VBScript support ?
Discontinue and break Classic ASP is just not possible : You should have realized it now at Microsoft.
We need reassurance : JScript and VBScript should remain available Server-Side.
Such little respect will have a high price: young managers at Microsoft do not even know what "was" VBScript : in fact? it "Was" not: it IS.
