In this blog, we will discuss the Microsoft plan to deprecate the VB scripting language. Below the details -
What is VBScript?
Visual Basic Scripting Edition, commonly referred to as VBScript, is a lightweight scripting language first introduced by Microsoft in 1996. The language has been available as a system component in Windows OS and has been widely used for automating tasks and controlling applications on Windows-based systems. It's often embedded within HTML pages to add dynamic interactivity and functionality to web pages and is commonly used in conjunction with Microsoft technologies like Active Server Pages (ASP) and Windows Script Host (WSH). However, with the advancement of technology, more modern and efficient options are now available.
Why is VBScript deprecated?
Technology has advanced over the years, giving rise to more powerful and versatile scripting languages such as JavaScript and PowerShell. These languages offer broader capabilities and are better suited for modern web development and automation tasks.
VBScript deprecation plan
Considering the decline in VBScript usage in favor of more modern web technologies, Microsoft have developed a phased deprecation plan for VBScript. Let's review the timeline of these changes.
In October 2023, Microsoft announced the commitment to providing the best and most efficient experiences by gradually deprecating VBScript. Beginning with the new OS release slated for later this year, VBScript will be available as features on demand (FODs). The feature will be completely retired from future Windows OS releases, as we transition to the more efficient PowerShell experiences.
Deprecation will occur in three phases.
Phase 1
In the first phase, VBScript FODs will be pre-installed in all Windows 11, version 24H2 and on by default. This helps ensure your experiences are not disrupted if you have a dependency on VBScript while you migrate your dependencies (applications, processes, and the like) away from VBScript. You can see the VBScript FODs enabled by default at Start > Settings > System > Optional features.
Screenshot of Windows System Settings shows VBScript installed under Optional features.
Phase 2
Around 2027, the VBScript FODs will no longer be enabled by default. This means that if you still rely on VBScript by that time, you'll need to enable the FODs to prevent your applications and processes from having problems.
Follow these steps if you need to continue using VBScript FODs:
- Go to Start > Settings > System > Optional features.
- Select View features next to “Add an Optional feature” option at the top.
- Type "VBSCRIPT" in the search dialog and select the check box next to the result.
- To enable the disabled feature, press Next.
Screenshot of a dialog box for adding an optional feature with a checkbox next to VBScript.
Phase 3
VBScript will be retired and eliminated from future versions of Windows. This means all the dynamic link libraries (.dll files) of VBScript will be removed. As a result, projects that rely on VBScript will stop functioning. By then, we expect that you'll have switched to suggested alternatives.
Reference -
https://techcommunity.microsoft.com/blog/windows-itpro-blog/vbscript-deprecation-timelines-and-next-steps/4148301
Created by Mohit Jain and Megha Gupta
No comments:
Post a Comment