VBScript deprecation: Timelines and next steps

Post by sancarn » Thu, Jun 06, 2024, 12:57 AM UTC

chem83 wrote: post #7

I find PowerShell, the language, verbose and not very ergonomic. This ship has sailed, but I wish Microsoft had done something to make Windows automation a little closer to other platforms, so that it could benefit from the good software that exists on other platforms. It seems that VBA will continue to exist as the programming front end for MS Office, which is unfortunate. They had announced Python support for Excel…

Post by dragonwriter » Thu, Jun 06, 2024, 1:02 AM UTC

Someone1234 wrote: post #16

zamadatix wrote: post #12

Earlier quoted context omitted.

It may have a separate timeline but it does seem to hint at going out the door in similar order on Office as well. I think the Python in Excel stuff is still in beta but things like lambdas, regex or Office Scripts all actually work (even on the web versions) and start taking big bites out of why you'd want to look at VB. New Outlook dropped VB support even on the desktop and I don't think they plan on maintaining se…

Python in Excel could have been amazing, except Microsoft executes it in a cloud environment and require a Cloud Service account to even open spreadsheets with it in. I'd strongly recommend people avoid Python in Excel, it is a Trojan Horse into forcing you to subscribe to access your own spreadsheets.

Post by sancarn » Thu, Jun 06, 2024, 1:11 AM UTC

draw_down wrote: post #3

Probably one of the most maddening things I have ever worked with, and that is saying something. Though a huge part of the blame for that goes to COM and registration, interop stuff, which is more Windows than VBScript and also probably never truly going away.