The implementation of many software projects requires at least two different languages: an industry-level one for the projects core, its powerful «engine», and a scripting language, which would be interpreted when the program is running. Scripting languages are typically simpler and slower than the industrial ones, but they have their own area of application. These languages are often used when the advanced users or third-party developers want to automate common tasks create their own parts of software logics.
Nevertheless, the paxScript.NET engine has none of those problems. The engine is rather small and lightweight and can be easily integrated into any .NET application. The languages paxScript.NET «understands» are the natural C#, VB.NET and Delphi.NET (with some useful syntactic sugar), and therefore the scripts can use any classes, structures, enumerations, arrays, delegates, events, and interfaces of a host application, as well as the host application can call the scripts methods. In additional, paxScript.NET comes with rich debugging capabilities.
paxScript.NET 2.7 The component implements C# and VB.NET interpreter written in C# which is possible to to embed into your WinForms or ASP.NET application so you can customize and extend the
ActiveXperts Scripting Toolkit 2.1 Call a VBScript function directly from your source code without invoking WSH, CSCRIPT or WSCRIPT. Use the function result directly. Set function timeout and catch exception
Malicious Mac OS X Script Poses Threat Although not yet found in the wild, the malicious script can harvest passwords and install remote control software and security backdoors onto a user's machine.