Recent content by Pieter Cooreman

That's exactly my assumption too.. But MicroSoft announced that VBScript will be totally removed from Windows OS. That includes their servers in my understanding...

i'm sorry for spamming... if you would be able to create a default.asp file, including nothing but: <% if 1=1 then response.write "hello" %> and your browser returns "hello", VBScript is still "around" somewhere in ASP.DLL, or IIS

What I have done sar: I have disabled WSH (Windows Scripting Host) on my Windows 10. .js and .vbs are not longer executed and return an error message. IIS however keeps on serving ASP/VBScript as if nothing happened.

The only 2 hosts that I have access to is my old Windows 10 laptop, and a production Windows Server 2019. None of these allow me to remove VBScript yet... I hope you can help me out, but I sure understand if that takes some time...

@LesFerch would you be so kind to post the error message you get when you request an .asp from your localhost in IIS? What exactly does IIS return when you request an asp page in case VBScript is deleted?

@LesFerch Yes sure, I'm aware VBScript has been taken out of Internet Explorer a while ago. But what I'm interested in here, is whether you can still use VBScript as server-side language in IIS on Windows 11 (in this case) after you've uninstalled it. Maybe Mr. Brink can shed a light? This would...

You're probably right. And that's why it's such a stupid decision. Windows hosting companies will no doubt keep on serving Classic ASP/VBScript. I can understand they disabled VBScript for Edge (MS had better removed Edge completely). But killing off a very popular scripting language, come'on.

Thanks! This is good to know. And it's very bad news. I'm still hosting 300 websites using Classic ASP/VBScript. No way I can update those to JScript or .NET...

After you remove VBScript, can you still use Classic ASP (using VBScript) on a Windows11, using IIS or IIS Express?