| • |
supports VB.NET, C#, JScript.NET and Java™† (J#)
languages |
|
| • |
supports both the .NET Framework Class Library (FCL) and
Microsoft's implementation of the Java™† JDK 1.1.4 libraries |
|
| • |
allows one to write .NET and Java™† applications without the
purchase of any additional products |
|
| • |
provides for the sharing of frameworks, objects, metadata and
code between Java and supported .NET languages |
|
| • |
a single Alintex script can contain multiple
script files in different languages |
|
| • |
within a script, a script file can
automatically access the functionality in other script files |
|
| • |
script files can be
reused across multiple scripts, providing an effective form of code
reuse |
|
| • |
automatic script caching and
referencing ensures minimal compilation across languages |
|
| • |
supports
typeless programming and late binding by default in the languages that
support it - VB.NET and JScript.NET |
|
| • |
JScript.NET offers
backwards compatibility with JScript by default |
|
| • |
support for new script language
file extensions allow a script to be executed by simply clicking on
it's icon |
|
| • |
offers
context menu integration with the Windows shell - allowing one to
perform various actions against a script by right-clicking it in Windows
Explorer. |
|
| • |
a compact
script #region code construct is provided as a quick and convenient
alternative to having to create a class/module/method code entry point |
|
| • |
command line
arguments are supported in all languages, including implicitly within a
script #region |
|
| • |
language
extensions are included to support access to application, environment
and script information at runtime |
|
| • |
additional
language extensions include support for a convenient new
"print" method and
InputBox dialog |
|
| • |
a
Gui/Cui/Unattended (GCU) design pattern, with supporting language
extensions, allows one to create a single script which can be run from the
command line, as a Windows application, or
unattended (no user interaction) |
|
| • |
supports the inclusion of
author, script and code information within the script itself - which
can then be retrieved at runtime |
|
| • |
multiple script files, script settings, author and script
information can be packed into a single
Portable Script File for convenient reuse and distribution |
|
| • |
a Portable Script File can be
unpacked to a folder, modified by the user, then
repacked back into a Portable Script File with a mouse click |
|
| • |
the contents of a Portable Script File are
self documenting and can be dynamically viewed in your web browser.
Author information, script information, script settings and code are all
displayed in the resulting web page |
|
| • |
both Console (AxScript)
and Windows (AxWscript)
application versions are included |
|
| • |
the Windows application (AxWscript)
captures and displays console output. Doing so allows it to offer the
versatility of running both command line and Windows targeted scripts |
|
| • |
AxWscript
supports a
user interface which includes a notification icon and context menu.
Scripts can be
terminated manually, or
automatically after a specified period of time. Errors can be
optionally written to the
application event log on supported operating systems |
|
| • |
built in diagnostic support allows one to
display the programmatic types contained in a script |
|
| • |
modular architecture allows the easy inclusion of additional
languages |
|
| • |
example scripts are provided in all supported languages |
|
| • |
a
Getting Started tutorial is included |
|
| • |
requires only the
installation of the free .NET Framework 1.1 Redistributable Package
(23Mb). Java™† (J#) support is optional and requires the installation of the
free Visual J# .NET Version 1.1 Redistributable Package (7Mb) |
|
| • |
runs on Windows 98, ME, NT, 2000, XP and Windows Server 2003 |
|
| • |
Alintex Script .NET is FREE for both personal and commercial
use |
|
