That's always been an intriguing property because it suggests the underlying SYS engine can support mulitple scripting languages. To my knowledge, no one has ever documented a method of switching to another language.
Another teaser is "External Module". While in Expert Mode, proceed to create a new Module and you'll notice that there are now two options:
New > Module and
New > External Module. It lets you specify the ProgID of a COM object or URI of a .NET assembly. I've never figured out how to use it and it is undocumented.
FWIW
You can access the .NET Framework from VBScript albeit just a few assemblies.
Alex Feinman explains how in this blog post.
You can also use
PowerShell from within VBScript. I realize that sounds a little odd, one scripting language calling another, but it has its merits. Powershell is the new gold standard for scripting in Windows. It has full access to the .NET Framework thereby allowing you to write very sophisticated scripts. SAPIEN Technologies offers a free ActiveX plugin,
called ActiveXPosh, that allows any COM-compatible language, such as VBScript, to invoke Powershell commands.
I've tried ActiveXPosh with Premise and it works ... although the test was very simple: Premise sent email using System.Net.Mail. A much more interesting test would be to collect some sort of data, chart it using .NET's
charting controls, generate a PNG file and then display it in Premise Browser.
