|Microsoft Pushing VBScript A Little Closer To the Edge|
|Written by Mike James|
|Wednesday, 14 August 2019|
of extinction. VBScript is one of the variations Microsoft created of the original VB. Now it has decided to drop default support in Internet Explorer. Clearly VBScript is on its way out.
As it happens HTAs were a great idea and well ahead of their time - sounds like a familiar Microsoft story when it comes to any attempt to move from a native Windows environment.
The latest announcement from Microsoft reads:
"The change to disable VBScript will take effect in the upcoming cumulative updates for Windows 7, 8, and 8.1 on August 13th, 2019. VBScript will be disabled by default for Internet Explorer 11 and WebOCs for Internet and Untrusted zones on all platforms running Internet Explorer 11. This change is effective for Internet Explorer 11 on Windows 10 as of the July 9th, 2019 cumulative updates."
You might wonder why Edge isn't included in the list of browsers not supporting VBS? The answer is Edge had already dumped a lot of Microsoft technology, ActiveX, Vector Markup Language and, of course, VBS.
So in the future any legacy website that uses VBS will need you to make a change to allow it to run. I can't imagine that there are many, but it gives you the overall direction of Microsoft's sentiments toward VBS and perhaps all its legacy Basics.
Of course, Microsoft is best remembered for killing Visual Basic 6 and replacing it with the incompatible, but arguably better, Visual Basic .NET. Leaving Visual Basic Script (VBS) and Visual Basic for Applications (VBA), both based on VB 6.
VBS never really caught on as a web scripting language, but it did become reasonably popular as a Windows scripting language. There are a lot of admin scripts written in VBS and it is important to note that these are not affected by the dropping of VBS from the legacy browsers.
So why has Microsoft a down on all things Basic?
or email your comment to: firstname.lastname@example.org
|Last Updated ( Wednesday, 14 August 2019 )|