What is the future for scripting in M-Files with the depreciation of VBscript by Microsoft?

We will start a communication and enablement plan on this later in the year, but my general guidance is to utilise the Vault Application Framework instead: The Vault Application Framework (m-files.com).  The VAF does currently still use VBScript proxies within the vault (VBScript reacts to the events and passes the data across to the VAF), but we are looking at ways to remove those proxies such that VAF applications can run even in scenarios where VBScript is not required.

We did actually test this out earlier in the year and it was successful, but we want to look again at the approach so that we can make it as seamless as possible for existing applications.

As a more general point: my personal strong recommendation is to not use VBScript in any new developments.  Whilst it's unlikely that Microsoft's deprecation will remove VBScript entirely from server environments in the immediate future, it will at some point and relying on VBScript for new installations seems like a very bad move.

I suppose that I should add that we have also tested out using some alternate scripting solutions to replace VBScript.  We do understand that for some customers and some resellers that using something less "heavy" than the VAF is useful.

We haven't got anything directly to announce here yet, but that requirement is understood.

I suppose that I should add that we have also tested out using some alternate scripting solutions to replace VBScript.  We do understand that for some customers and some resellers that using something less "heavy" than the VAF is useful.

We haven't got anything directly to announce here yet, but that requirement is understood.