MicrosoftNaveen_Shankar you may have noticed that this article is one of the most read articles in this Windows IT Pro Blog. It's actually the 3rd most read article for 2024 so far. Well done!
But there's a good reason for that: people are worried about MicroSoft's plans to remove VBScript. I am too. I'm a Classic ASP developer. I recently wrote a book about Classic ASP: https://demo.asplite.com/ebook.asp. You may not have the time to read it through, or you may not know Classic ASP very well, but Classic ASP was a very popular web development toolbox back in 1996-2005. Classic ASP web applications relied on mainly 2 Active Scripting Languages: VBScript and JScript. 90% of the Classic ASP developers use and used VBScript. For more than 25 years now, millions of websites, web applications, intranets, extranets, forums, interactive forms, shopping carts, CMS, CRM and anything else you can think of, rely on this Classic ASP/VBScript tandem.
First tests show that when VBScript is removed from a Windows host, IIS returns a 500 error message when an ASP page (using VBScript) is requested. Removing VBScript tears down millions of web applications, businesses, public services and who knows what and who else will be affected by this. It is unimaginable. Nobody can truly predict what will possibly go wrong and how many tragic side-effects removing VBScript will have.
We therefore need a clear answer on how the decision of removing VBScript will affect web applications built on Classic ASP/VBScript. Thank you. We also started a petition to ask MicroSoft to reconsider the decision to remove VBscript: https://www.change.org/p/ask-microsoft-to-cancel-their-planned-deprecation-of-vbscript-classic-asp. Lots of people sign it.
