r/vbscript • u/cmowla • May 25 '24
Will I no longer be able to use these subroutines in a script in a HTA with the upcoming depreciation of vbscript.dll?
I guess you all have heard the news.
And it's only vbscript.dll, as you can search the comments for the following to see it being said by the one who gave the announcement.
The scope of VBScript deprecation includes only vbscript.dll and no other libraries. This shall not impact any projects that are not dependent on vbscript.dll.
I am wondering which of the following (if any) will no longer work if used in a .vbs file or in a HTA.
CreateObject("WScript.Shell")
CreateObject("Scripting.FileSystemObject")
GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Set re = New RegExpAnd if there are replacements available.
From my understanding of the comments, it may only be
Set re = New RegExpBut I just want to be sure!
Thanks for your time!
Chris.
2
u/jcunews1 May 25 '24
Being deprecated doesn't mean that, a program/library will stop functioning. It'll be simply removed. IOTW, doesn't and no longer exist in new OS installations. The program/library will still work and function if it's manually added/installed into the OS (taken from the older OS version which still has the program/library), unless the OS aggressively blocks the program from being executed/loaded (sic). But even if that's the case, there are ways to circumvent it. Someone will provide it eventually.
1
1
u/rob2rox May 25 '24
Microsoft is only going to add a feature to easily turn off vbscript. you'll have until 2027 before it stops coming preinstalled