Alintex Script users should note the following language specific issues.

 

 

VB.NET

 

1. Typeless Programming

 

Alintex Script supports typeless programming with VB.NET by default.

 

Unlike the default options for VB.NET, Alintex Script does not require the explicit declaration of variables.  All undeclared variables in Alintex Script VB.NET scripts are of Object type.

 

Users can specify that all variables need to be explicitly declared by adding the following statement to the top of a VB.NET script:-

 

Option Explicit On

 

Placing this statement at the top of a script produces the same VB.NET compiler behavior as the default.

 

See the VB.NET Compiler documentation for additional information.

 

2. Microsoft.VisualBasic.dll

 

Alintex Script automatically references the Microsoft.VisualBasic.dll assembly, and imports the Microsoft.VisualBasic namespace for VB.NET scripts.

 

3. Script #Region

 

Alintex Script supports a script #region in VB.NET code as an alternative to providing a traditional .NET application entry point.  See Script #Region for further information.

 

4. Print Method

 

Alintex Script supports the use of a "print" method as an alternative to System.Console.WriteLine.  See print Method for further information.

 

 

---

C#

 

1. Script #Region

 

Alintex Script supports a script #region in C# code as an alternative to providing a traditional .NET application entry point.  See Script #Region for further information.

 

2. Print Method

 

Alintex Script supports the use of a "print" method as an alternative to System.Console.WriteLine.  See print Method for further information.

 

 

---

JScript.NET

 

1.  JScript Compatibility

 

By default, JScript.NET scripts in Alintex Script offer typeless programming and provide full backward language compatibility with previous versions of JScript.  This behavior is in contrast with the default JScript.NET settings, but is in keeping with Alintex Script being a scripting product.  See the /fast option for further information.

 

2. Global Code and Script #Region

 

As JScript.NET supports global code, there is no need to specify an explicit entry point.  Because of this, the Alintex Script script #region feature is not applicable to JScript.NET scripts.

 

3. Command Line Arguments

 

When determining the arguments passed on the command line in a JScript.NET script, it is recommended that you use the ScriptHost.Arguments property.  See the commandLine.jsx script in your tutorial folder for an example.

 

 

---

Java™† (J#)

 

1.  File Extensions

 

Alintex Script supports the .vjx and .vj file extensions for J#, as well as the standard - .jsl.  See File Extensions for more information.

 

2. Script #Region

 

Alintex Script supports a script #region in J# code as an alternative to providing a traditional application entry point.  See Script #Region for further information.

 

3. Throws Declaration

 

Java (J#) specifies "throws java.lang.Exception, System.Exception" as part of the J# script #region declaration.  See Item 2 above.

 

4. Print Method

 

Alintex Script supports the use of a "print" method as an alternative to System.out.println or System.Console.WriteLine. 

 

Java (J#) users should be aware that unlike System.Console.WriteLine, System.out.println is not captured by the AxWscript console window.  It is therefore recommended that you use the  or System.Console.WriteLine as an alternative.

 

 

 

       

       Visual J# .NET has been developed independently by Microsoft.  It is neither endorsed nor approved by Sun Microsystems, Inc.

       No support is provided for JNI, RMI and Applets